Load problems with 2.3 server.

Katsuhiro Kondou kondou at nec.co.jp
Mon Oct 16 04:26:52 UTC 2000


In article <Pine.LNX.4.02.10010161100150.1115-100000 at firewater.ihug.co.nz>,
	Simon Lyall <simon.lyall at ihug.co.nz> wrote;

} should be okay. The innd process is very large most of the time ( 998MB
} right now with 816MB resident).

How large dbz files?  Here shows mine, and innd consumes
about 380MB as resident.
# ls -l history*
-rw-rw-r--   1 news     news     826795443 Oct 16 13:16 history
-rw-rw-r--   1 news     news         120 Oct 16 13:16 history.dir
-rw-rw-r--   1 news     news     155573196 Oct 16 04:00 history.hash
-rw-rw-r--   1 news     news     207430928 Oct 16 13:16 history.index

} The machine also consumes open files like there is no tomorrow, I have
} bunmped the max of these up to 32768 which appears to be enough for now,
} right now it's using 12,000 odd with only 30 readers and 20 feed
} connections.

If you skip SMsetup(SM_PREOPEN) in nnrpd.c, nnrpd only
opens when needed.  But this will lead performance
problem if nnrpdcheckart is set to true.

} Does anybody have any pointers to possible solutions (hopefully other than
} adding more RAM)? .

How about tagged hash history, though you cannot use it
over 2GB?
-- 
Katsuhiro Kondou



More information about the inn-workers mailing list