From: Jack E. <ja...@lo...> - 2006-07-13 23:21:56
|
Matt, MY leak is absolutely tied to weather_graph... Or maybe not the leak, but the long PAUSE... Like clockwork! I tried to collect data for Matt to analyze by setting my debug=weather_graph Well it paused extra long: 230+ seconds!! And it spit tons and tons of info onto the screen... But when I looked inside the logs, I saw very little. NONE of the debug info was there... What needs to be changed to allow the debug info to be logged...? Maybe it oughta have a log of it's own, as there is SO much info... It seemed to pause for a second in between every single graph, too. Is there a possibly unnecessary delay in this routine?? It the pause intentional? How fast a CPU does one need to crunch the numbers every time the graphs have to be made? And... Does it HAVE to graph for periods where these is no data? Beyond last month, my RRD is empty. Yet it makes graphs for those periods anyway! Blank ones that seem to take just as long as graphs where data exists. When it was broken, the pauses were shorter than ever! Like maybe 13 seconds... Why it takes THAT long to do nothing, I can only guess: A pause in the code that needs to be removed, perhaps? This package needs to be streamlined. My two cents... Jack :) >Tim, > >do you mind sending me, off-list, a copy of your mh_temp.user_code? I would >like to see if anything is being done in an obviously incorrect way by mh. > >thanks, >Matt > |