Skip to content

(new) new relic 结果详细解释

OrlandoLee edited this page Sep 29, 2013 · 1 revision

1. Have workers at the ready


Request queuing: The wait time between the web server and the application code. Most customers will be lucky enough to not see this in their graphs. If you do see time being spent here, it’s time to provision some more servers to handle the load. Speeding up your app will also help here. The faster your app, the faster it can pick the next request off the queue.

2. Speed up the back-end


Web application: The time spent in the application code. If only there was an app performance tool that could let you find out how to optimize your web application! That would be sweet.

3. Improve the speed of light


Network: The time it takes for a request to make a round-trip over the internet. Improve the speed of light and BAM! Faster internet. Until you get that sorted out, you might consider moving static assets closer to your customers. User your real-user data to see which countries are having the worst experience and make sure your new CDN provider has sufficient service in those locations.

4. Trim down that DOM


DOM Processing: Time spent in the browser parsing and interpreting the HTML. This just in: Huge pages take a long time to parse! Taking a look at your pages and see if there might be some belt tightening to do.

5. Do less work


Page Rendering: Time spent in the browser displaying the HTML, running in-line JavaScript and loading images. Downloading large assets and running in-line JavaScript can take a significant amount of time for many apps. Check to see which browsers spend the most time here, too. You may find some significant differences in performance that can be improved by using different JavaScript techniques.

Clone this wiki locally