3 ms·
Not encouraging that in the first graph they truncate the y-scale to make the performance appear three times better visually, while it is actually 40% better.
by jjgreen 3y ago
Not encouraging that in the first graph they truncate the y-scale to make the performance appear three times better visually, while it is actually 40% better.
- chomp 3y agoI don’t see how you could get misled when the peaks are annotated and immediately and clearly visible.
- fintler 3y agoThe graph is zoomed in. The Y axis doesn't start at zero, so it appears to be a larger difference at first glance than it actually is.
- rewmie 3y ago> I don’t see how you could get misled when the peaks are annotated and immediately and clearly visible. This is a textbook graphing error, or worse graphing manipulation. Humans perceive proportions, and not including the origin of a graph gets these plots out of whack.
- jjgreen 3y agoIndeed, see for example https://www.heap.io/blog/how-to-lie-with-data-visualization https://www.heap.io/blog/how-to-lie-with-data-visualization
- otikik 3y agoI see how someone can avoid being misled, but I don’t see how can someone not see someone being misled.
- _a_a_a_ 3y agoIt's perfectly clear to me. Little scope for confusion IMO.
- mellosouls 3y ago"High speed," "minimum latency," and "ultimate performance" are often used to characterize Apache APISIX. "Highly misleading graphs" now as well. Perhaps it is best to charitably assume an oversight rather than a deliberate misrepresentation for PR reasons - which obviously would not lend credence to the product.
- gnutrino 3y agoIt appears they are making an assumption that the type of person who reads blog posts about the inner workings of an API gateway also knows how to read a well labeled graph.