INN not keeping up with incoming news

[Katsuhiro Kondou]

In article <72bssluy1v.fsf at nd1.eng.demon.net>,
	Alex Kiernan <alexk at demon.net> wrote;

} My suspicion is the history performance problem is platform dependent
} - what platforms are people running on (we're using Solaris 2.6/8 and
} seeing it)?

I think it depends on how much memory the server has.  Mine in
production has 4GB, which Fabien said was not in the problem.
While, on my testing box(1GB mem) it's in the case(hishave and
hiswrite consumes 1/3 cpu time).  I think it's due to looking
thru mmapp'ed region(history.hash) everytime(in most case)
dbzexists() and dbzstore() are called.  I think this could be
improved by returning pointer of empty entry if dbzexists()
returns FALSE.  The pointer is also cached on pre-commit cache
so that it can be used by dbzstore().

I know Russ is thinking history api, but I think not a few people
cannot wait until it's done.
-- 
Katsuhiro Kondou