Thanks everyone for your answers, I'll just answer this mail, because
it contains everything that has been said.

On 20/02/2011 11:50, Thilo Schulz wrote:
> On Sunday, 20. February 2011 02:51:01 Dominic Fandrey wrote:
>>> This was expected that some users will experience that problem. What is
>>> your operating system and distribution? And most importantly: what is
>>> your system Hz setting if there exists something like this?
>>
>> Operating system: FreeBSD 8-stable development branch
> 
> Interesting. I've had a FreeBSD user tell me there's no problem with the 
> recent changes.
> ...

Once I was told it's about scheduler frequency it became clear it's my
fault.

>> Hz: according to xrandr 60
> 
> I'm not talking about your monitor, I am talking about your system Hz 
> setting, 
> or kernel Hz. It should be at least 1000Hz, which will yield a 1ms precision.

Which is exactly what it isn't. I turned my machine down to 200Hz so
that the CPU can reach the C3 sleep state. I also use a less precise
timer than the default CPU internal timer, because that one is turned
off in C3.

> 
> You can use com_busywait of course and this will be pretty much the old 
> behaviour. But it means that your client will unnecessarily hog 100% of your 
> CPU, even if your framerate hits com_maxfps. Note that this is how it was 
> before for framerates > about 100fps; my new changes fix this. But they 
> require a granularity for the timeout of the select() system call of at least 
> 1ms. Most major OS, including Windows and MacOSX seem to fulfill this 
> requirement, that's why I turned this on per default.

You're right, it makes sense. Still I prefer busywait for my notebook,
because of the (measurable) increased battery runtime for using C3
states. And it's only a single core any way.

Regards

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 
_______________________________________________
ioquake3 mailing list
[email protected]
http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
By sending this message I agree to love ioquake3 and libsdl.

Reply via email to