INN not keeping up with incoming news

[Fabien Tassin]

According to Russ Allbery:
> 
> So superficially it looked like it worked at first.

Yes.
 
> hiswrite is *still* quite fast but hishave is incredibly slow.  Weird.
> And that persisted even after a complete reboot:

Yes but after a few hours, it is back to more normal values.
 
> and also sent your hiswrite times back to where they were before?  That's
> really, really strange.  Nothing happened to your history cache somehow,
> did it?  What are the history cache statistics reporting?  Are you still
> getting the same hit/miss ratios?

I should have waited a little bit longer between each operation.
It looks like the history cache needs about 2 hours to be efficient.
(hiscachesize = 256)

Here is the report from midnight to now (10:00) :

history lookup   00:11:09.237   1.9%    5566034     0.002      0.120      1.278
history sync     00:00:00.447   0.0%      11147     0.000      0.040      1.245
history write    00:11:53.662   2.0%     553999     0.060      1.288     15.988
idle             06:49:42.143  68.9%   58625006     0.307      0.419      1.658

now, with mlock() and a stabilized cache :

history lookup   00:00:07.197   0.0%    3084827     0.002      0.002      0.003
history sync     00:00:00.166   0.0%       6122     0.000      0.027      0.073
history write    00:00:21.417   0.1%     304396     0.060      0.070      0.084
idle             04:16:36.521  72.3%   37348633     0.329      0.412      0.546

I wonder why it took that long for the history cache to be efficient...

-- 
Fabien Tassin -+- fta at sofaraway.org