Skip to content

Commit

Permalink
fix(apm): made changes to the definition of wall clock time
Browse files Browse the repository at this point in the history
  • Loading branch information
homelessbirds committed Apr 9, 2024
1 parent 1ee28da commit 35435ce
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -48,9 +48,9 @@ The <DoNotTranslate>**Transactions**</DoNotTranslate> page also may include link

## Wall-clock time [#wall_clock_time]

Wall-clock time measures "real-time elapsed" during a specific transaction. For example, you're using a program to monitor transaction speeds. According to the program, the transaction took 30 seconds to complete, but one minute passed in the real world or on the wall clock due to discrepancies across the program. New Relic uses wall-clock time for all the transactions and then sums that value across all of the transactions.
Wall-clock time measures "real-time elapsed" during a specific transaction. For example, you're an engineer responsible for managing the checkout experience on a e-commerce site. You would like to understand how long it takes for a customer to add an item to their cart The transaction itself took 30 seconds to complete but one minute in the real world or on the "wall clock". This discrepancy in time could be because the function had to wait for network calls or other inputs and outputs and that waiting time is not accounted. New Relic uses wall-clock time for all the transactions and then sums that value across all of the transactions.

The host can execute requests in parallel so that you may see percentages over 100. For example, 100% would indicate that the execution time across all selected transactions equals the time expended when recording wall-clock time.
In the above example, let's imagine that when a customer adds an item to their cart the host can execute requests in parallel. One of these functions might take 3 seconds to complete and the other would takes 2 seconds but, because they were happening simultaneously, the customer only had to wait 3 seconds. Because of this parallel work, you may see percentages over 100. For example, 100% would indicate that the execution time across all selected transactions equals the time expended when recording wall-clock time.

## View transactions [#tx_viewing]

Expand Down

0 comments on commit 35435ce

Please sign in to comment.