lHi, If you don't need asynchrony pvsync2 tends to be good. If you do I think the only choice from the engines listed is posixaio... Regarding libaio, see my earlier reply to Mark... PS: VMware is spelt with a lowercase w - http://thelowercasew.com/about . On Wed, 24 Oct 2018 at 05:27, Eliezer Nebab <eliezer@integritech.solutions> wrote: > > Mark, > > > Finally had a chance to try this out this weekend. > > > VMWare version: > > # vmware -v > VMware ESXi 6.5.0 build-8294253 > > > I built the docker file per your procedure, but I excluded the line that Sitsofe mentioned ("RUN git config --global http.sslVerify false") and started docker exactly the way you described. > > I then copied the ID: > > # docker cp 997cd757e1f1d350e353bd6b4a252c5b16497e49d0b4ed46e32273dc 6a82aa56:/fio/fio . > # ls -l > total 5832 > -rw-r--r--. 1 root root 341 Oct 23 22:39 Dockerfile > -rwxr-xr-x. 1 root root 5951600 Oct 23 22:46 fio > > > I scp'd the "fio" file to my esxi server. > > To my excitement, tried to run "fio" with the libaio which did not work. The only engines available out of that fio build are as follows: > > /tmp/fio --enghelp > > > Available IO engines: > cpuio > mmap > sync > psync > vsync > pvsync > pvsync2 > null > net > netsplice > ftruncate > filecreate > posixaio > falloc > e4defrag > splice > mtd > sg > > Otherwise, fio is working just as you described. Thank you very much Mark!!! > > So, out of the engines listed above, which ioengine would be suitable to use for VMWare testing? -- Sitsofe | http://sucs.org/~sits/
