Hi, On Thu, Sep 24, 2009 at 06:17:55PM +0200, Sebastian Harl wrote: > Okay, so it seems we've got a rather major speed-down in rrdgraph Sarge > ??? Etch (RRDtool 1.0 ??? 1.2) and another one Etch ??? Lenny (RRDtool 1.2 ??? > 1.3). In the former case, RRDtool switched from using libgd to libart > for doing the graphing, in the latter case, they switched to libcairo > (and libpango). I'm pretty sure, the speed-down is related to that. In > the course of the 1.3.x releases some optimizations have been applied > which improved the effect a bit but there still is a notable speed-down. > > Anyway, frankly, I've got no idea what to do about that.
well, I think that's a good explanation. So it's not a "bug", but an intentional design decision with not-so-intentional side effects. I don't know about upstream's motivation for those switches, but perhaps it would be worthwhile to benchmark graphing with the different libraries / RRDtool versions and reevaluate their merits in that light? If upstream is willing to think in those directions, "wishlist" might be appropriate, otherwise I'd think it would be useful to document that an FPU is essential, and graphing more than 30-50 machines or so will require *significant* resources -- wait, I'm thinking munin here... "wontfix, bloat, by design"? Florian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
