|
Joe,Cool. Although you do seem to have about 5% "missing" meaning system jobs are eating your CPU. But if hits aren't causing that much load anymore, then you may be right that you were in the midst of an "anomalous event" <grin>.
I am not a performance guru by any stretch and perhaps looking at WRKACTJOB is the wrong way to go about determining "load". Here is a screen shot: http://www.petesworkshop.com/i/wrkactjob.jpg . All other jobs listed below this shot show 0 CPU usage. When I hit the site now, there is no change in overall CPU utilization so perhaps yesterday's events were anomaly. In any case, the http filtering stopped whatever events were sapping the CPU.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.