3 ms·
A couple of questions: - What does the top chart represent that blends into the background? - What is so costly about rendering pages for Googlebot that it ta
by pestaa 14y ago
A couple of questions:
- What does the top chart represent that blends into the background?
- What is so costly about rendering pages for Googlebot that it takes almost twice as long as the average rendering time for public views? The throughput is especially interesting as it is less than 30% of its public equivalent.
- What does 1 cpu unit equal to?
- Also interesting to me is the fact that API requests require the most horsepower, yet also provide almost the lowest response time and very high throughput. How API requests are so different from "browser" requests, since I suspect both are powered by the same backend?
Sorry for my naivety.
- kneath 14y agoThe top chart is the throughput for the whole stack over the time period listed in the dropdown. Googlebot tends toward the opposite of the pages we optimize for. For example, Googlebot is really interested in the 38,291th page of your history. I think 1 CPU unit is a core, but I'm not sure. It's mostly interesting in terms of relative numbers. And yes, both api and the web live in the same application servers.
- pestaa 14y agoThanks for your answers, nice insight. Great job on the dashboard, its interface is really inspiring. I still don't grasp how API can be so efficient while doing basically the same thing as the public-facing site minus probably the HTML rendering, which leads me to believe that rendering is damn resource-heavy in Rails.
- kneath 14y agoKeep in mind that a huge portion of our requests are rendering code. Syntax highlighted code. With line numbers.