I don't know if I would call it difficult change, but it's a different method of generating the graph. Currently rrdtool writes to standard output and that gets sent straight to the client (after the HTTP header). The --lazy option obviously only works for writing to a file, which means the frontend will need a place to store those graphs. That's do-able, but it means additional I/O for the server which the current solution avoids - not to mention the additional time to generate the graphs due to waiting for I/O. I'm a bit perplexed about where to go with the graphs. There are a lot of possibilities for highly compressed dynamic updates with SVG-based graphs, but not directly from rrdtool's SVG output.
-Matt Jesse Becker wrote: > [EMAIL PROTECTED] wrote: >> I've been working on a list of ways to improve the PHP web >> frontend. Just curious what every else thinks of these. >> >> - add support for a caching layer for generated graphs >> Add code that allows caching of generated graphs, either on the >> filesystem or in a memcache cache. When generating a graph, serve >> the cached version if the refresh time for that metric has not passed. > > The rrdtool program already has a "--lazy" option that will (quoting > from the rrdgraph man page): "[o]nly generate the graph if the current > graph is out of date or not existent." > > While not a complete in-ganglia solution, it should be an easy change. > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
