Alastair Grant wrote:

For those of you with pingboost questions, here's the old explanation
of how the -pingboost options work, as posted by Alfred
[mailto:[EMAIL PROTECTED] Friday, July 12, 2002:

All the pingboot modes attempt to reduce the latency caused by the
server.
The default implementation adds around 20msec to each players ping
(under linux).

Mode "1" reduces this by using a different wait method (a select()
call). This method reduces the latency to 10msec.

Mode "2" uses a similar but slightly different method (and alarm() type
call). Again, the result it 10msec worth of latency being added. NOTE
that this method has the potential to hang a server in certain
(terminal) situations. If anyone has used this mode recently (not the
first test we did!) and it hangs please speak up :)

Mode "3" minimises the latency to the minimum possible level by
processing a frame EVERY time a packet arrives. This causes the lowest
possible latency, but can also cause extreme CPU usages (it does a
complete frame for every packet, with each player sending lots of
packets per second and 30 players this adds up to insane amounts of
frames). Use this mode at your own risk, it will consume all available
CPU, don't complain that cstrike uses too much CPU if you use this mode
:-)  In a future release this mode will be tweaked to let the admin
balance latencies agains CPU usage (by processing a frame every N
packets).

There is also an external modules called "pingbooster" by UDPSoft (or is
it UDPSoftware?). They implement something like mode "3". As this is an
external module, and was built for an older version of HL (1108) it may
not work properly any longer, and future releases may (accidently) break
it.


-- Wireplay Official http://www.wireplay.co.uk/


In fact, this old explantation is simply wrong, while was quoted many
and many times on hlds_linux last year.
Should be:

[...]

Mode "2" reduces this by using a different wait method (a select()
call). This method reduces the latency to 10msec.

Mode "1" uses a similar but slightly different method (and alarm() type
call). Again, the result it 10msec worth of latency being added. NOTE
that this method has the potential to hang a server in certain
(terminal) situations. If anyone has used this mode recently (not the
first test we did!) and it hangs please speak up :)

[...]

For those, who still doubts in my words - simply run strace on a hlds
process and look on output.

Yury Pshenichny.


_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to