History cache performance?

Andrew A. Vasilyev andy at demos.su
Thu Mar 8 17:46:18 UTC 2001


>   BTW: anyone tried playing with locking the cache in memory? I tried
> using a locked shared mem, but I didn't see a benefit. My machine had
> lots of memory, though. I would expect the cache to stay in memory on a
> loaded machine, but comments here made me try it.

  Here are some figures from innreport pages:

BEFORE:

Code region        Time      Pct  Invoked Min(ms) Avg(ms) Max(ms)
history lookup 06:43:48.356 28.2% 6241842 0.770 3.882 7.822 
history lookup 07:30:05.843 31.2% 7770452 1.009 3.475 7.321 
history lookup 07:39:22.008 32.1% 6273851 1.423 4.393 8.108 

AFTER:

history lookup 01:17:32.400 5.4% 6599560 0.320 0.705 2.293 
history lookup 01:42:45.898 7.2% 6891548 0.400 0.895 3.115 
history lookup 01:43:30.782 7.2% 7327713 0.353 0.848 1.902 

  So the benefit for lookup time is about 5 times.
  Solaris 2.6 at E450 2x300MHz, 1GB RAM. INN 1.7.2 with redesigned
  main select loop, but this is probably negligible for history
  lookups, I think.

  Any other statistics available on demand :-))
________
	ANDY


More information about the inn-workers mailing list