The licensed version of the software can handle around 2 million messages per hour and the freeware version about 300000 per hour. The licensed version has been regularly tested to handle 400-600 messages per second while logging to file.
From version 7.1.0. more messages buffers have been added which should improve the performance significantly.
The licensed version has been increased to have a 20000 message buffer, while the freeware has a 500 message buffer.
If you suspect that you may be loosing messages then have a look at the File | Debug options | View message buffer option to check that the "Message Queue overflow:" value is always 0. This indicates the amount of messages that have been dropped. If you are running the Service version then this same information can be found from the Manage | Debug options menu.
If you find that it is performing slowly, then the best solution is to disable the display option since you won't be able to read that many messages anyway and displaying the messages slows it down. You may want to modify the devices configuration to only send messages that meet a set level. There is no point in logging everything if you only discard these messages later. Normally debug level messages don't need to be logged. The scheduled archiving can be used to move the log files off the disk or zip them up and save space. An option to delete old logs is currently being developed.
From version 7.0.2, the ODBC logging function has been improved and is easily able to handle 100 messages per second. These figures were achieved when testing against MS Access, MS SQL and MySQL databases. Other database vendors may provide different results.
The best way to see if Kiwi Syslog Daemon does what you want is to give it a try. Kiwi SyslogGen is great for doing just this.
27th of August, 2010
Thank you for rating this answer.