Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'The Final Answer' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
The Final Answer
Authored by: Notch Johnson on Dec 07, '03 09:57:43AM

One more test I think would be informative:

1) Get your computer to a state where sysctl is displaying an incorrect value.

2) Run the benchtests or anything else that stresses the CPU, perhaps a dnet client with priority set to 0.

3) Immediately recheck the sysctl number.

This would tell if processor cycling is happening. The bench of CPU intensive app would elevate the clock speed to the maximum and rechecking sysctl should report a number that makes us happy.



[ Reply to This | # ]