<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> Karl, My apologies for the speeeling mistook, I thought I had fixed all of these. Will send in a new version (and patches later today). I am running a production framework using these systems and yes the compile time does predominate on the plugin execution (but I think if the figures I am getting out of Perl are right then it did anyway). Key thing is are the module files in the filing system cache! Overall monitoring load has not increased by any measurable amount, with each probe running every 5 minutes (Nagios reports 35.1% of checks completed within 5 minutes and 100% in 15 minutes) . Check latency has been decreased slightly if you believe the figures but is within the error margin. Some of this will be from the few small gains made by code getting rewritten to be simpler once the argument parsing is removed from the main flow. My later plugin attempt, which are still to be sent out, result in generally smaller and easier to understand (I think) code. The biggest overhead is the pre-defined Parameters that are exported for convenience from Plugin::Parameter. I am thinking on moving these to another module set, but then we are into more files for less code. I could of course adopt a shorter naming convention, but I had hoped that the efficiency of the Perl parser/lexer would make this unnecessary. ePN should win big with this I would have thought but cannot test this yet, as I need to get our distributed framework up on more machines and need the auto learning facility urgently. I note you comment about the `human' readable output in the check_game patch and will abandon this approach (except for internal use) for now until I can duplicate the perl library approach with the C framework. Will hammer on the code a bit more later today to get some error reporting integrated and write a surrounding document to describe the use of the framework once it is fully ready. Regards, Howard. Karl DeBisschop wrote: <blockquote type="cite" cite="mid20040331014539.42a13efd.karl@debisschop.net"> <pre wrap="">On Tue, 30 Mar 2004 19:52:35 +0100 Howard Wilkinson <a class="moz-txt-link-rfc2396E" href="mailto:howard@cohtech.com"><howard@cohtech.com></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">I distributed the wrong files for the perl framework. Here are the fixed and working ones I should have sent out!. </pre> </blockquote> <pre wrap=""> A couple of comments. First, I do appreciate that this framework does a great job of providing a large base of usable code. Kudos. I would imagine there's more than a few hours of work in there. One trivial issue - you have 'warrenty' for 'warranty' - obivously a lesser concern in the variable/method names but it is also present on the output. If 'warrenty' is a non-US variant spelling, I'm not familiar with it. Can that be changed? What I do really wonder about is the overall weight of these modules - there are 70 KB of modules for plugins that used to weigh in at only 8 KB to begin with. If embedded perl does what it's supposed to, this all gets compiled only once, I hope. But if a user is not running embedded perl, the sheer weight of code could have real performance impacts. So overall, I'd like to move to this new frameowrk if the potential performance impacts can be evaluated and found to be managable in some way. And thanks for this effort, it clearly is a step forward. -- Karl </pre> </blockquote> <div class="moz-signature">-- <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <title>Signature</title> <table cellpadding="2" cellspacing="2" border="0" style="text-align: left; width: 100%;"> <tbody> <tr> <td style="vertical-align: top;">Howard Wilkinson </td> <td style="vertical-align: top;">Phone: </td> <td style="vertical-align: top;">+44(20)7690 7075 </td> </tr> <tr> <td style="vertical-align: top;">Coherent Technology Limited </td> <td style="vertical-align: top;">Fax: </td> <td style="vertical-align: top;">+44(20)79230110 </td> </tr> <tr> <td style="vertical-align: top;">33 Belgrade Road, Stoke Newington, </td> <td style="vertical-align: top;">Mobile: </td> <td style="vertical-align: top;">+44(7980)639379 </td> </tr> <tr> <td style="vertical-align: top;">London, United Kingdom, N16 8DH </td> <td style="vertical-align: top;">Email: </td> <td style="vertical-align: top;"><a name="howardcohtech.com" target="mailto:howard@cohtech.com" href="mailto:howard@cohtech.com"></a><a class="moz-txt-link-abbreviated" href="mailto:howard@cohtech.com">howard@cohtech.com</a> </td> </tr> </tbody> </table> </div> <DIV><HR> This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from you system. E-mail transmission cannot be guarenteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. </DIV> </body> </html>