Doing or Waiting?
Briefly

Doing or Waiting?
"Observability allows you to determine what your applications are waiting on, and if you have enough visibility, it will allow you to determine where the time is being spent."
"In the example above, the performance issue was caused by indirect waits, and the resolution was to modify the configuration of the antivirus software to prevent it from blocking the file server."
"When looking into why the queries were taking so long, you would find that they were waiting for blocks to be read from the disk into the buffer cache memory of the database server."
Observability is crucial for understanding application performance and identifying wait times. In a case study, increased response times were linked to indirect waits caused by antivirus software blocking file server access. By modifying antivirus configurations, the issue was resolved. Historically, monolithic applications faced similar challenges with relational databases, where queries were delayed due to waiting for disk blocks to be read into memory. Monitoring tools often suggested adding resources to alleviate these performance bottlenecks.
Read at New Relic
Unable to calculate read time
[
|
]