Doing or Waiting?
Blog post from New Relic
Applications and services operate in two states: doing tasks or waiting for events, similar to driving with either movement or pauses. Efficient performance requires minimizing wait times, whether due to direct waits (waiting for other systems) or indirect waits (CPU unavailability due to other processes). Understanding where time is spent can help optimize performance by reducing unnecessary waits and enhancing CPU usage efficiency. Observability tools, such as Application Performance Monitoring (APM) and Distributed Tracing, enable the identification of bottlenecks and offer insights into improving application performance by monitoring interactions between systems and infrastructure. By identifying the reasons behind waits and optimizing code or infrastructure, businesses can improve application performance and reduce costs, as demonstrated by real-world cases where tweaking configurations and optimizing queries led to reduced wait times and enhanced processing efficiency.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Observability | 5 | 3,204 | 716 | 172 | +14% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.