Skip to content
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.

Graph rendering in Descartes #130

Closed
abhinav-sbu opened this issue Jul 13, 2013 · 1 comment
Closed

Graph rendering in Descartes #130

abhinav-sbu opened this issue Jul 13, 2013 · 1 comment

Comments

@abhinav-sbu
Copy link

Hi,

I was looking at the way graphs are rendered in case of Descartes. It seems that it gets the graphs in png or svg(if specified) format from Graphite and displays that. So ,does Descartes offer any performance improvement in terms of graph rendering compared to Graphite ?
(In my case, I am applying multiple functions on graph data while getting it from Graphite. So, it takes around 30 secs , in getting the graph in browser. I am wondering if Descartes can offer better performance in terms of graph rendering compared to Graphite.)

@obfuscurity
Copy link
Owner

Descartes uses Graphite as the datastore and rendering API for all graph images. The only exception (currently) are the sparklines in the Metrics tab, which are rendered client-side with D3.js. But it still queries Graphite for all data. Therefore, if your Graphite is slow, Descartes will be slow. If Graphite is fast, Descartes will be fast.

I would start with making your Graphite faster. Sure, there's an outside chance that your Graphite is choking on pycairo rendering only, but that seems unlikely. There is an issue for client-side rendering but I don't have an ETA for when this feature will be shipped.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants