[syslog-ng] Syslog-ng load testing

Vaibhav Goel vgoel at cucbc.com
Thu Sep 28 19:50:41 CEST 2006


Thanks Nate,  I am on a similar path.  Already hacked out a perl script
and I will share it with the world when its more meaningful.  So far its
just generically opening a socket to syslog-ng and sending messages to
it like crazy.  Already seeing some interesting results....



-----Original Message-----
From: syslog-ng-bounces at lists.balabit.hu
[mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of Nate Campi
Sent: September 28, 2006 10:12 AM
To: Syslog-ng users' and developers' mailing list
Subject: Re: [syslog-ng] Syslog-ng load testing

On Thu, Sep 28, 2006 at 09:36:10AM -0700, Vaibhav Goel wrote:
> 
> I am planning to do some capacity and load testing our syslog-ng
servers
> over TCP.  Towards that end, I will be writing a script to send
packets
> to a syslog-ng host.  Has anyone done anything similar?  I was just
> thinking of writing a simple script that will open multiple sockets to
> the server and send a message (based upon our current calculated
average
> message size).  Any other suggestions are appreciated.

The graphs here:

 http://www.campin.net/syslog-ng/faq.html#perf

Are from a perl script that simply looks in syslog-ng logs for a
particular "starting test" string that includes how many test messages
are going to be sent, then looks for that many messages all with a
sequence number appended to real-world syslog messages (a collection of
about 50 messages I grabbed), then reports any numbers missing from the
sequence when it gets near the total number of messages (doesn't depend
on the actual last log making it in case it's lost), and reports on the
time period between when the first and last message were logged to the
file.

Pretty simple. I did the log scraper in perl to generate those graphs
via gd::graph or something like that, but you could just spit out CSV
and graph it with something like (*gasp*) Excel.

I can't share those scripts since they were written while working for a
large, evil corporation, but the logic is quite simple. I had it measure
CPU and also network stats (network stats were a separate graph not
pictured on the site) but that's certainly not mandatory. Just make sure
that if you measure CPU that you also see how much CPU the
testing/analysis script uses - might be more than you'd think.
-- 
Nate

There are two ways to write error-free programs. Only the third one
works.  -Anon.  

_______________________________________________
syslog-ng maillist  -  syslog-ng at lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html





More information about the syslog-ng mailing list