Lag and other ill effects.

LogD parses all the string logging data that the engine calls the alert api with. That information is parsed/decoded by doing text analysis character by character on the incoming string.

Textual analysis in this manner is CPU intensive. Effort has been made to keep LogD running as fast and as smoothly as possible in order to not lag the server. However, it is impossible to do the work without using more resources than a standard HLDS/Admin setup.

In most server systems, this resource hit should not make too much of a difference. However, it is up to the server operator to decide whether the resource hit is acceptable or not. If you are running a relatively slow system, or you have problems with your current resources, you will probably notice lag or sluggishness with the use of LogD.

There is nothing we can do about this. We have worked to keep resource use as low as possible in order that as many people as possible can benefit from LogD. We will continue to optimise it as far as we are able to, but please do not complain if you cant get it working without lag.

Note that the above is merly a disclaimer. In reality after putting LogD in the field, their have been extremely few reports on LogD causing lag. It appears to work just fine on even 32 player servers.