Cygwin Filesystem Performance degradation 1.7.5 vs 1.7.7, and methods for improving performance

Derry Shribman
Wed Oct 13 15:34:00 GMT 2010


 >> set CYGWIN=fsaccess:noacl,file_cache
 > All the features in this patch (except for the "noacl") do not require any
 > configuration, since there is no 'loss of behavior' or 'loss of correctness'.
 > st_ino, st_nlink behave as before. Symlink and executable script detection
 > behave as before (just faster...).
 > Yoni is preparing a patch to submit that will not include the noacl feature,
 > and thus will not include any CYGWIN env related stuff.

Clarification (since it was not clear from my previous post): in the initial 
patch Yoni submitted, ALL the new features were controllable via the CYGWIN env, 
only for our testing purposes.
We used it to run the lstat and 'ls -l' performance test code with each feature 
enabled/disabled in order to validate it works correctly and that it really 
improves performance.

This control via CYGWIN env is NOT to be left in the production code. It was 
only for testing. In the next patch Yoni will be sending, they will not include 
CYGWIN env control for these features, except for the "noacl" - which will be in 
a separate noacl patch.


More information about the Cygwin-developers mailing list