Re: high CPU usage

From: Alex Brooks <ambr@dont-contact.us>
Date: Fri, 26 Nov 1999 21:22:01 +1100 (EST)

> > 1999/11/25 23:17:06| storeRebuildFromSwapLog: SWAP_LOG_ADD
> > D71ABA1EB53281AE594D35A28F97C152 000068D8
>
> This is only seen while Squid is rebuilding it's cache index after a
> restart.

Yes, you're absolutely right of course. The reason I'm seeing it is
because I upped the debug level in squid.conf, then got it to re-read its
config file by restarting it - thus the only time I looked at it was when
it had just been restarted. When I did it with squid -k reconfigure it
didn't give me the same stuff.

Now the thing it seems to be doing the most of is outputting messages
like:

1999/11/26 21:20:22| storeMaintainSwapSpace stats:
1999/11/26 21:20:22| 182905 objects
1999/11/26 21:20:22| 158 were scanned
1999/11/26 21:20:22| 0 were locked
1999/11/26 21:20:22| 0 were expired
1999/11/26 21:20:24| comm_select: 0 FDs ready at 943611624
1999/11/26 21:20:24| comm_select: time out: 943611624
1999/11/26 21:20:24| eventRun: RUN ID 44702
1999/11/26 21:20:24| eventRun: Running 'MaintainSwapSpace', id 44701
1999/11/26 21:20:24| eventAdd: Adding 'MaintainSwapSpace', in 0.853200
seconds
1999/11/26 21:20:24| storeMaintainSwapSpace: f=0.146800, max_scan=158,
max_remove=20

Although these aren't coming out quite as fast as the previous ones were.
Does this mean anything to anyone?

Alex
Received on Fri Nov 26 1999 - 03:42:19 MST

This archive was generated by hypermail pre-2.1.9 : Wed Apr 09 2008 - 11:57:32 MDT