next up previous contents
Next: Quake II latency Up: Performance Issues Previous: Performance Issues

Resource usage

rq2proxy doesn't handle significant amounts of data (typically 2k/player/s), so doesn't use significant amounts of CPU. If POSIX real-time scheduling is used, rq2proxy will use more CPU than with real-time scheduling disabled, but this is still no more than about 5% of the CPU time of a 486DX2/66.

More important is memory usage: to avoid double-free()ing bugs, rq2proxy doesn't free() nearly as much memory as it should do--all temporary buffers allocated at parse time, for example, are never freed. The result is that with memory locking on, each instance of either rq2ps or rq2pc uses about 1Mbyte of unswappable, real memory. This isn't nearly as nasty as it used to be, given the recent dramatic fall in memory prices, but it's much worse than it should be: the next version hopes to clean this up--if you email me saying you need this feature, it will be bumped up the priority queue.



Richard Watts
1998-12-22