INN not keeping up with incoming news

[Russ Allbery]

Fabien Tassin <fta at sofaraway.org> writes:
> According to Fabien Tassin:

>> I've tried to mlock() only history.index.

>> Before :
>> hiswrite 41992(5063)
>> hiswrite 40724(5485)
>> 
>> After :
>> hiswrite 339(5054)
>> hiswrite 374(5513)

So superficially it looked like it worked at first.  But after expire ran

> Feb 26 00:19:24 newsfeed innd: ME time 300053 idle 176034(360970) hishave 41945(65663) hiswrite 4411(5727) hissync 2(115)
> Feb 26 00:24:24 newsfeed innd: ME time 300000 idle 177631(489361) hishave 31161(58454) hiswrite 335(5172) hissync 5(104)

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

> Feb 26 01:11:24 newsfeed innd: ME time 300000 idle 101941(321621) hishave 42396(71520) hiswrite 71023(9156) hissync 9(183)
> Feb 26 01:16:24 newsfeed innd: ME time 300000 idle 121642(383617) hishave 28648(58090) hiswrite 54546(6594) hissync 8(132)

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?

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>