On Wed, 2005-11-16 at 01:05 -0800, Hans Reiser wrote: > Craig Shelley wrote: > > >On Tue, 2005-11-15 at 19:04 +0100, Laurent Riffard wrote: > > > > > >>Please, could you do it again with the -T option for strace? It will > >>show the time spent in system calls. > >> > >> > >> > >[EMAIL PROTECTED]:~$ strace -T -p 8002 2>&1 | grep fsync > >fsync(26) = 0 <0.566159> > >fsync(26) = 0 <0.159852> > >fsync(26) = 0 <0.179659> > >fsync(26) = 0 <0.153406> > >fsync(26) = 0 <0.136685> > >fsync(26) = 0 <0.171057> > >fsync(26) = 0 <0.165733> > >fsync(26) = 0 <0.178846> > >fsync(26) = 0 <0.186595> > >fsync(26) = 0 <0.184368> > >fsync(26) = 0 <0.177273> > >fsync(26) = 0 <0.178634> > >fsync(26) = 0 <0.181036> > >fsync(26) = 0 <0.178750> > >fsync(26) = 0 <0.324480> > >fsync(26) = 0 <0.177226> > >fsync(26) = 0 <0.184625> > >fsync(26) = 0 <0.186224> > >fsync(26) = 0 <0.177282> > >fsync(26) = 0 <0.177146> > >fsync(26) = 0 <0.176000> > >fsync(26) = 0 <0.192434> > >fsync(26) = 0 <0.177482> > >fsync(26) = 0 <0.183357> > >fsync(26) = 0 <0.176528> > >fsync(26) = 0 <0.184334> > >fsync(26) = 0 <0.176622> > >fsync(26) = 0 <0.177977> > >fsync(26) = 0 <0.178636> > >fsync(26) = 0 <0.259863> > >fsync(26) = 0 <0.172789> > >fsync(26) = 0 <0.171739> > >fsync(26) = 0 <0.179641> > >fsync(26) = 0 <0.178157> > >fsync(26) = 0 <0.180272> > >fsync(26) = 0 <0.170426> > >fsync(26) = 0 <0.187630> > >fsync(26) = 0 <0.171589> > >fsync(26) = 0 <0.178135> > > > > > >I seem to be finding that the performance of the system degrades with > >time and file system usage. > >Openoffice really starts to run slow after a while. Just as an > >experiment, I did > >ls -R /usr > >The directory listing appeared very quickly with hardly any hard disk > >access. Then shortly later when switching back to Openoffice, the > >process froze for about 3 minutes with continuous hard disk access. > > > >One thing which may be relevant is that my kernel is patched with > >Suspend2 and FBsplash, although I can't remember having any problems > >like this before. > > > >Many Thanks, > > > > > > > could you define what the numbers mean (what units, what is measured)?
I believe the value inside < > is the time spent in the system call in seconds. In the above list, evolution seemed to be calling fsync() as fast as it could. Although the fd remains at 26 in this case, it closes and re-opens the file between calls to fsync(). I seem to notice that the length of time spent in the fsync() calls depends to some degree on how much hard disk activity there has been since the last call. The strange thing is this seems to apply to reading also, so performing an ls -R /, and stopping it after a few seconds. Shortly later, some process will block for tens of seconds when it next calls fsync(). -- Craig Shelley EMail: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
