At 03:10 PM 11/12/2008, Ryan Devonshire wrote:
>This is the output from one of our servers, it is consistent throughout
>- and this is running Fedora 6 with a 2.6.x kernel (recompiled). The CPU
>usage is reported falsely, server is running on a Q6600.
>
>20:08:05 stats
>20:08:06 CPU In Out Uptime Users FPS Players
> 99.90 81.89 119.89 122 16 1000.00 10
>20:08:06 stats
>20:08:06 CPU In Out Uptime Users FPS Players
> 99.90 85.18 125.19 122 16 1000.00 10
>20:08:06 stats
>20:08:06 CPU In Out Uptime Users FPS Players
> 99.90 84.30 123.78 122 16 1000.00 10
>20:08:06 stats
>20:08:06 CPU In Out Uptime Users FPS Players
> 99.90 84.06 122.97 122 16 1000.00 10
>20:08:06 stats
>20:08:06 CPU In Out Uptime Users FPS Players
> 99.90 84.22 121.49 122 16 919.96 10
You're never going to get 1000 all the time, no matter who says what.
from the usleep() man page:
BUGS
Probably not accurate on many machines down to the
microsecond. Count on precision only to -4 or maybe -5.
G. "Monk" Stanley
<gary at summit-servers dot com | gary at DragonflyBSD dot org>
http://leaf.dragonflybsd.org/~gary
"There currently are 7 different ways to get time from a computer.
All of them can't agree on how long a second is supposed to be" -Me
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
