4 ms·
Bad form? It was hard to represent the data with a 0 to max Y-axis. Should I make a note of it?
by uggedal 17y ago
Bad form? It was hard to represent the data with a 0 to max Y-axis. Should I make a note of it?
- icey 17y agoThe labels seemed clear to me; I don't think it's a big deal personally.
- barrkel 17y agoIt makes it hard to draw conclusions like 1x vs 4x scaling for hosts with 1 VCPU vs 4 VCPUs.
- bdr 17y agoI think so. It's an easy-to-miss detail that really changes your perception of the data. Ideally the graph would indicate this itself by having a broken axis, but that's probably a pain to do.
- uggedal 17y agoI included a note at the top of the article. The graphs are from Google's API and were a pain to get in the state they are now. Not going to change them in this lifetime;-)
- bdr 17y agoYep. For Python there's a good-enough client for the graph API called "graphy", I think it's on Google Code.
- pierrefar 17y agoCan you please release the actual numbers that you plotted?
- uggedal 17y agohttp://github.com/uggedal/vpsbench http://github.com/uggedal/vpsbench has all the data and scripts used.
- albertsun 17y agoThe convention I've used is that this is okay for line graphs like the ones that you've used, but not okay for bar graphs.
- gojomo 17y agoIt also depends on whether the main purpose of the graph is to show changes along the ranged axis (as if from period to period over time), or the magnitude of differences between the lines on the ranged axis. If the latter, a zero origin is fairer. While the day-to-day differences are of some interest here, the main interest is provider vs. provider, so the axes are not ideal. They make the provider-to-provider differences seem larger.