You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: