The 6th Annual All Day DevOps conference took place on October 28, 2021, featuring architect Ram Lakshmanan's webinar on "7 habits of highly effective Performance Troubleshooters." The presentation covered strategies for forecasting problems, immediate response actions, root cause identification, and prevention of future issues.
The performance testing of the Spring Pet Clinic application revealed significant insights. Key findings included an overall response time of up to 9.14 seconds, high CPU utilization at 97.90%, and a concerning 61% memory wastage due to inefficient programming. Other issues observed were lack of disk space and spikes in CPU time.
When an application is under-allocated memory, performance issues arise, including degraded transaction response times, increased CPU usage, and potential OutOfMemoryErrors. Proactively analyzing garbage collection logs can help identify memory allocation problems. Monitoring specific patterns in these logs enables developers to diagnose whether more memory is needed or if a memory leak exists.
The post discusses various garbage collection (GC) patterns observable in applications, including healthy saw-tooth patterns, heavy caching, acute memory leaks, consecutive full GC, and metaspace memory problems. By analyzing these patterns, developers can assess application performance and identify potential memory issues, ultimately improving application health and efficiency.
On October 11, 2021, GCeasy experienced an outage due to HTTP 504 errors when customers uploaded logs, traced to a new code deployment on October 9. Monitoring revealed increased CPU and database connections. A root cause analysis using yCrash identified an inefficient SQL query, leading to timeouts. Removing the query restored functionality.
The 'java.lang.System.getProperty()' API is used to retrieve system properties in Java applications. However, its synchronized nature can lead to performance issues, especially if called in critical code paths, causing threads to become BLOCKED. Solutions include upgrading to JDK 11 or caching properties to enhance performance.
The author reflects on their journey from monolithic to microservice architecture, highlighting a large financial institution's transition from a CORBA/C++ platform to SOAP/Java. They express concerns about modern microservices consuming significantly more memory and facing degraded response times compared to older monolithic systems, while acknowledging the benefits of microservices.
Naveen Kumar Namachivayam hosted Ram Lakshmanan, the architect of yCrash, at the Performance Engineers Clubhouse. They discussed several key topics including the fundamentals of Garbage Collection, the significance of memory management, and an introduction to GC throughput, providing valuable insights for performance engineers.
The 'Kill Process or sacrifice child' OutOfMemoryError occurs when memory usage exceeds available RAM, prompting the OS to terminate certain processes. A simulation using an AWS EC2 instance demonstrated this error, where a Java application and a chaotic BuggyApp exceeded memory limits. Potential solutions include increasing RAM, reducing processes, and optimizing memory use.
The 'ping' command is essential for diagnosing network issues by checking host reachability via ICMP packets. It measures round-trip times and reports packet losses, errors, and TTL values, varying by operating system. Common issues include timeouts and unreachable hosts, with solutions provided for resolution. Performance tools may enhance troubleshooting.