>> I just tried monitoring the start of collectl with another >> copy running at a monitoring interval of .1 and watching all CPUs with >> -sC. I did see one hit 100% but only for 1 cycle. > > When I use the .1 s interval, the precision is much lower, everything > is a multiple of 10 and the instance of collectl that is doing the > monitoring takes about 30% of the CPU. Most intervals have 100% user, > but the few sys spikes are much higher than before, up to 50%. >
I'd think the precision would be much higher since you're not taking 10 samples/sec >> I don't think I >> could easily make some of the code conditionally load because it's too >> intertwined. > > OK, thanks for considering it and for all the suggestions above. > > By scattering a few print statements throughout collectl, I see that > most of the time is spent loading and parsing the files collectl > (before first line of code) and formatit.ph (require > "$ReqDir/formatit.ph"). This is why I was hoping that separate files > could be loaded depending on the usage; reading system information, > writing daemon raw files, reading daemon raw files, outputting to > console. > have you timed collectl running as a daemon? when I first wrote collectl over 10 years ago I was running on much smaller boxes and performance issues were a bigger issue, but even then things really went fast. my initial thought was to put everything collectl needed for formatting output into formatit and everything else in the main section so we are on the same page. as it turned out the main init routine gets called in both places so formatit has to get loaded anyways AND I've strayed from my original plan and have stuck other routines in formatit that may not be related to printing, again because perl has always shown to be so fast. all that said, have you see the --utime switch (I've got switches for everything). you can use it to tell collectl to write special timestamps into the raw file to allow you to literally see how much time to the usec is spent in the data collection section. might prove illuminating for you. or not... -mark ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Collectl-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/collectl-interest
