RE: [hobbit] Xymon 4.3.0: Beta version available on Sourceforge

["Cleaver, Japheth" <jcleaver (at) soe.sony.com>]

> -----Original Message-----
> From: Rich Smrcina [mailto:rsmrcina (at) wi.rr.com]
> Sent: Monday, February 09, 2009 6:38 PM
> To: hobbit (at) hswn.dk
> Subject: Re: [hobbit] Xymon 4.3.0: Beta version available on
Sourceforge
> 
 
> A good number of db applications are implemented in a multi-tier
> configuration where the
> db server is separate from the app server.  Xymon wouldn't necessarily
be
> different in
> that respect.
> 
> My suggestion would be to leave the database location up to the
> implementation.
> 
> Now you perl zealots will probably freak out, but I probably wouldn't
want
> that database
> code to be in Perl (sorry Japeth), it's too performance sensitive.


Well, the actual injection within DBI::mysql is done through XS using
the MySQL development libraries, so it's not just pure perl code
running. More importantly, since hobbitd_channel keeps a pipe open to a
persistent perl process (it's not being forked every time a new status
message comes in) there isn't any compilation penalty for using perl as
opposed to something else -- it's only executed once. Properly written,
you're keeping a statement handle open and just inserting as fast as you
can -- I suspect it will be "fast enough" for most purposes.

It's a trade-off in flexibility, I'd much rather have a live-hackable
perl script gluing things together instead of C code that the end user
is going to have to recompile when something changes.

Best of all.... with the channel architecture people can easily roll
their own, too :)

-jc