Post by account_disabled on Dec 26, 2023 0:40:04 GMT -5
The procedure you will need to follow to identify a slow loading page is quite simple: Duplicate the slow transaction. Look for the transaction in the list of slow transactions in New Relic. Review the transaction summary and trace the details to determine what is driving the slow performance. Let's look at an example of this and how New Relic can be used to diagnose this problem. Step 1: Duplicate the Transaction Let's see an example. Our client experiences slow loading every time a single blog post loads. All other pages load normally, but individual posts take several seconds to load. So, the first step is to duplicate the problem. In this case, that means visiting a single blog post several times to ensure that New Relic captures the data it needs.
If your site uses page caching, which is built into our Kinsta platform, you will need to clear Buy Bulk SMS Service the cache between page loads. Otherwise you will end up loading the page from cache rather than forcing WordPress to generate the page. Step 2: Find the Slow Transaction After duplicating the slow transaction, go to New Relic and select the Transactions tab. Then scroll down until you see the list of slow transactions, at the bottom right of the New relic dashboard. List of slow transactions in New Relic Slow transactions in New Relic Click the transaction you are debugging to view the details. After selecting the transaction, a summary of the transaction will be displayed. A summary of a single slow transaction in New Relic APM.
Slow transaction summary The summary allows you to see a snapshot of the components that contributed to the transaction processing time. In the case of our example transaction, a call to an external resource, www.googleapis.com, is responsible for 5,000 milliseconds of a transaction that took a total of 5,350 milliseconds to complete. While this is useful information, the track details tab will provide the data you need to understand exactly what's happening. Slow transaction trace details in New Relic Slow transaction trace details The trace details tab provides a detailed hierarchical waterfall that shows the function, database queries, and external calls processed by PHP as it generates the page. In the case of our example transaction, the trace details reveal that a call to a Google Analytics URL slows down the process. If we work backwards from that request, we see that a PHP function called gapp_get_post_pageviews.
If your site uses page caching, which is built into our Kinsta platform, you will need to clear Buy Bulk SMS Service the cache between page loads. Otherwise you will end up loading the page from cache rather than forcing WordPress to generate the page. Step 2: Find the Slow Transaction After duplicating the slow transaction, go to New Relic and select the Transactions tab. Then scroll down until you see the list of slow transactions, at the bottom right of the New relic dashboard. List of slow transactions in New Relic Slow transactions in New Relic Click the transaction you are debugging to view the details. After selecting the transaction, a summary of the transaction will be displayed. A summary of a single slow transaction in New Relic APM.
Slow transaction summary The summary allows you to see a snapshot of the components that contributed to the transaction processing time. In the case of our example transaction, a call to an external resource, www.googleapis.com, is responsible for 5,000 milliseconds of a transaction that took a total of 5,350 milliseconds to complete. While this is useful information, the track details tab will provide the data you need to understand exactly what's happening. Slow transaction trace details in New Relic Slow transaction trace details The trace details tab provides a detailed hierarchical waterfall that shows the function, database queries, and external calls processed by PHP as it generates the page. In the case of our example transaction, the trace details reveal that a call to a Google Analytics URL slows down the process. If we work backwards from that request, we see that a PHP function called gapp_get_post_pageviews.