Question about "<news>/db/history" file size
rra at stanford.edu
Thu Apr 23 18:02:26 UTC 2009
Petr Novopashenniy <pety at rusnet.ru> writes:
> But expire process uses ~1 GBytes of memory.
> When history file was ~4,5 GBytes (two weeks ago), expire process uses
> more than 1,2 GBytes of memory. Yes, looks like "expire process size"
> = ~"history.index size".
Yeah, innd has more locality to its writes, but expire writes all over
> Maybe it is possible not do full memory map (at one time) for history file
> index (for expire process)?
It'll be dog-slow.
> And, also, it is possible show number of articles in cnfs buffers (in
> "cnfsstat -a" output)?
> Something like this:
> Buffer news1, size: 47.7 GBytes, position: 28.3 GBytes 10.59 cycles
> Articles count: xxxx?
I believe the CNFS metadata doesn't actually store that information.
> And, if expire process not shutdown correctly, innd remains in "reserved"
> mode. How I can "ureserve" innd without restart?
ctlinnd go 'reason matching the reserve reason'
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the inn-workers