If you are an app developer, you know what typical latency you get. This page serves its purpose: to let you know if there is something unusual. What's the big deal?
It's a big deal because it's showing averages for all responses. I might, on average, get crappy responses for my app, but everyone else might be getting good ones on the whole. Without a scale on the graph, I have no idea what I'm getting is "normal" or not, and may overlook something obvious, like my connection to my server, causing the issue.
Why are we jumping on Facebook for this? Google does this all the time with e.g. their search volume graphs. Perhaps Facebook is simply trying to show relative.
Admittedly, the unit on these graphs is quite important while the search volume unit isn't (as) important.
Adding a Y axis would immediately draw up hundreds of blog posts and academic papers citing it as a "benchmark", making various claims and hypotheticals about Facebook's infrastructure. Since we don't have access to the exact metric or method of measurement, the exact magnitude is arguably meaningless.
Also, since this has potential for FUD and Facebook-bashing, it's in their interest to not publish raw numbers.
13 comments
[ 2.3 ms ] story [ 30.9 ms ] threadAdmittedly, the unit on these graphs is quite important while the search volume unit isn't (as) important.
Also, since this has potential for FUD and Facebook-bashing, it's in their interest to not publish raw numbers.