Skip to content
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.

Memory Usage idea #39

Open
slant opened this issue Jul 10, 2013 · 2 comments
Open

Memory Usage idea #39

slant opened this issue Jul 10, 2013 · 2 comments

Comments

@slant
Copy link

slant commented Jul 10, 2013

It occurred to me that while having a numeric value for Average and Max is useful to us developer-minded folk, a visual interpretation would likely be quite beneficial to many people.

This might look like a thin bar, the left side indicating 0MB and the far right indicating either 512MB or 1024MB depending on the dyno size. Two markers could be placed on this line to indicate minimum and maximum, which move around upon these metrics being updated. The are of the line between the two might be brighter to indicate relevance.

I say this realizing that we don't have a Min visible right now, but do we have this and it's just hidden? If not, then perhaps the other marker would be the average.

Using this data, in either case, we might even output a concurrent web worker recommendation: "You could fit 4 workers into a single dyno at this rate."

All just thoughts. I just know that people tend to like visuals for this kind of data.

@RyanBalfanz
Copy link

Sounds like a less complicated bullet graph: http://en.wikipedia.org/wiki/Bullet_graph

@slant
Copy link
Author

slant commented Sep 10, 2013

Well put. I suppose it kinda does resemble that.

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

No branches or pull requests

2 participants