Quake 2 runs at 100% CPU
It's always 100% and it does not let go. It looks very similar to RAM benchmarking.
VaeVictis:i find it funny that you even consider grammar a sign of intelligence, that itself is a very uneducated claim
Virtually all Q2 clients and servers are single threaded. I have never heard of anyone making a multi-threaded version.
If you are seeing 100% CPU usage in Windows on an idle Q2 server then you have screwed up your Windows scheduling or messed with the code in Q2 to cause it. Either that, or your running a computer from 1986.
When I say %100 cpu I refer to one logical processor unit. On my single core its one hyperthread.The only thing I could get out of strace that seems to occupy the majority is "gettimeofday ({##,##}, {###,###})" = 0 # being numbers. Which is very similar to KDE traces which are usually filled with those gettimeofdays. KDE is C++ but I think it is the libc time getting function. KDE does not run 100% but then again the gettimeofday's are slightly less frequent and they subside to some extent eventually. Makes it very difficult to trace bugs.In Q2 they appear in blocks of about 20 gettimeofday's. There is also a clock_gettime(CLOCK_MONOTONIC, {###,###}) = 0also in blocks of 10-20, interspersed in the trace that does appear to be overtly connected with the gettimeofday.When I run on the run level daemon, the daemon handler probably some how puts a check on the gettimeofday function through libc. It probably running in between the program and the libc. Its job is to handle these things after all.Which may explain why when I run under the daemon -- I can't jump very high. Sort of.Urban terror also runs in a similar fashion.All this is fine by me anyways, I was just wondering if there was conclusively a rational for running consecutive calls to the time. Which if you did not know happens during server client sync. Maybe in other instances. Perhaps several functions all call for time and the time calls all get executed at once. Which would mencingly suggest its ease of aggregation in one single time call with 0 rewrite. No?Other interesting things in strace.... when handswitching, you can see the array search of the the config settings for the static change on the local client. It searches until it finds it. So if this and other game action sets where on top it would perhaps leave open the possibility of slightly optimized usage. Although the overhead for that array is nearly nil it is getting stronger everyday.