This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re[2]: Cygwin performance (was [ANN] PW32 the...)
- To: Chris Faylor <cygwin-developers at sourceware dot cygnus dot com>
- Subject: Re[2]: Cygwin performance (was [ANN] PW32 the...)
- From: Egor Duda <deo at logos-m dot ru>
- Date: Wed, 15 Mar 2000 18:55:44 +0300
- CC: cygdev <cygwin-developers at sourceware dot cygnus dot com>
- Organization: DEO
- References: <20000315091124.I19524@cygnus.com>
- Reply-To: Egor Duda <deo at logos-m dot ru>
Hi!
Mar 15 2000, Chris Faylor cgf@cygnus.com wrote:
>>No matter of the possible speed up, I don't like this solution
>>because of...
>>
>>> note: you have to recompile your application to utilize "stat_lite"
>>> function.
>>
>>... that result.
CF> I think that Egor also provided a CYGWIN environment variable setting
CF> method, too.
no.
>>Ah, one hint: This wouldn't change anything when ntsec is OFF. But
>>in that case neither get_file_owner() nor get_file_group() nor
>>get_file_attribute() could slowing down things...
CF> I think that the big slowdown happens in counting the files in
CF> a directory to update the "nlinks" field in stat (or whatever
CF> it's called).
ah, yes. nlinks too.
CF> I went over the file handling code a year or so ago and attempted
CF> to eliminate multiple hits to the disk as much as possible. I'm
CF> sure that more can be done here, though.
CF> Maybe we should just detect when a file or directory is remote
CF> and not do some of the more expensive operations.
CF> I would like the ability to be able to set attributes on an executable
CF> something like:
CF> chattr --stat-lite ls.exe
well, perhaps that's a way. but anyway, i think that application author or
porter should be able to "set" this flag on per-call-basis. if in some
function he don't need inode, nlinks, but only st_size and st_atime he
can give "stat" a hint.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19