Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a graph cache #29

Open
orithena opened this issue Dec 20, 2012 · 2 comments
Open

Need a graph cache #29

orithena opened this issue Dec 20, 2012 · 2 comments

Comments

@orithena
Copy link
Owner

Graph generation has become too expensive. We need a cache and invalidate mechanism...

@thegcat
Copy link

thegcat commented Jun 2, 2014

Seconded, though I'm not entirely sure if the current code doesn't do it already?

1 idea that could be implemented rather shortly:

  • A Graph is valid until the next kill, if kills are timestamped this changes the complexity from "create a graph on each request" to "a data roundtrip and time comparison on each request + a graph on the first request after a kill". The last kill could even be denormalized to the game/round object, but that's probably not necessary.

1 idea for which I'm not sure how difficult it would be:

  • Move the rendering to the client and serve an svg for f* sake. The only reason that comes to mind to mind to use a bitmap format to show a graph is compatibility with the client, which shouldn't be a consideration anymore in the 2010s 😑 😳

@thegcat
Copy link

thegcat commented Jun 2, 2014

Oh, and should the graphs generated by graphviz not render nicely in sag, one could also try some R instead.

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

No branches or pull requests

2 participants