Yep - absolutely.
>> Using x86_64/cygwin1-20150223.dll.xz??
>>
>> ~ uname -a
>> CYGWIN_NT-6.1 DEHAGART-WS02 1.7.35s(0.286/5/3) 20150223 21:02:38 x86_64
>> Cygwin
>>
>> ~ cat /etc/nsswitch.conf
>> passwd: db
>> group: db
>>
>> First manual start of bash shell *seemed* to take slightly longer than
>> before and slightly longer than files db setting.
>> But anyway, the timed results show this:
>>
>> cmd /v:on /c "echo !TIME! & C:\cygwin64\bin\mintty.exe /bin/echo "test" &
>> echo !TIME!"
>>
>> C:\Users\dehagart>cmd /v:on /c "echo !TIME! & C:\cygwin64\bin\mintty.exe
>> /bin/echo "test" & echo !TIME!"
>> 14:22:01.74
>> 14:22:02.56 00:00.82
>>
>> C:\Users\dehagart>cmd /v:on /c "echo !TIME! & C:\cygwin64\bin\mintty.exe
>> /bin/echo "test" & echo !TIME!"
>> 14:22:07.10
>> 14:22:07.27 00:00.17
>>
>> C:\Users\dehagart>cmd /v:on /c "echo !TIME! & C:\cygwin64\bin\mintty.exe
>> /bin/echo "test" & echo !TIME!"
>> 14:22:08.99
>> 14:22:09.16 00:00.17
>>
>> C:\Users\dehagart>cmd /v:on /c "echo !TIME! & C:\cygwin64\bin\mintty.exe
>> /bin/echo "test" & echo !TIME!"
>> 14:22:10.72
>> 14:22:10.89 00:00.17
>>
>> I.e. significantly better.
>
>Excellent! Is that something you can live with, including the
>occassional longer time(*)?
>
> (*) Which is probably some background effect, probably mostly to do with
> OS caching stuff.
