FYI i have sent a pull request https://github.com/axboe/fio/pull/64 which makes fio on windows on par with iometer. The difference quite big on our local flash machines (60k iops to 100k) On Sat, Apr 25, 2015 at 1:43 PM, Iuliu Rus <iuliur@xxxxxxxxxx> wrote: > It however did create the fio.exe after i commented out the include. > Thanks! We'll submit a patch once we figure out why the queue depth is > not working. > BTW this is Google Compute Engine team, and we're using fio to compare > our windows and linux storage performance. > > On Sat, Apr 25, 2015 at 1:35 PM, Iuliu Rus <iuliur@xxxxxxxxxx> wrote: >> It doesn't create fio.exe for me. I commented that include out since >> it doesn't look like it's needed, but then linker complains about mmap >> munmap and sysconfig. >> >> >> On Sat, Apr 25, 2015 at 12:46 PM, Bruce Cran <bruce@xxxxxxxxxxx> wrote: >>> I've been meaning to investigate that build failure: it does, however get as far as creating the fio.exe binary so you can ignore the error. >>> >>> -- >>> Bruce >>> >>>> On Apr 25, 2015, at 12:04, Iuliu Rus <iuliur@xxxxxxxxxx> wrote: >>>> >>>> Hello, >>>> Looking at fio for windows, we are pretty sure that the queue depth >>>> parameter is not working. >>>> We wanted to investigate this ourselves and prepare a fix, but the >>>> windows build is not working either. From a cygwin64 shell, make clean >>>> and make -j results in this: >>>> t/dedupe.c:13:23: fatal error: sys/ioctl.h: No such file or directory >>>> (although i see ioctl.h under cygwin64\usr\include\sys and under >>>> cygwin64\usr\i686-pc-cygwin\sys-root\usr\include\sys). >>>> Any idea why the build fails? >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe fio" in >>>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
