Re: Re2: file weirdness / vnlru process issues

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:
:Oct 19 01:13:40 apocalypse kernel: HLX
:
:but cvsup eats too much cpu, while updating - 75%-85%, but while fetching
:only new files only 5% of cpu.
:
:-- 

    Well, you have to realize that cvsup is basically stat()ing every single
    file in your CVS or source tree.  If they are all cached, then there will
    be no I/O and cvsup will be cpu bound.  It's only a bug if cvsup takes
    an inordinately long time to do its work.  e.g. do a 'systat -vm 1' and
    look at the namecache hits... if you get high numbers like 10,000-100,000
    hits/sec then there is nothing wrong, cvsup is just stat()ing a lot of
    cached files.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>