--- title: On the Case – High Resource Usage description: A customer recently submitted a case that Pedro Principeza, a Canonical Support Engineer, was able to solve using an interesting technique. Principeza was contacted to help pinpoint the processes that were generating a high rate of I/O operations, affecting server performance. Implementing a trace to pinpoint workload usage was the best s […] url: https://canonical.com/blog/on-the-case-high-resource-usage?format=md --- 1. [Blog](https://canonical.com/blog) 2. Article --- [Canonical](https://canonical.com/blog/author/canonical "More about Canonical") 11 April 2019 # On the Case – High Resource Usage [Canonical](https://canonical.com/blog/tag/canonical) [jbd2](https://canonical.com/blog/tag/jbd2) [Server](https://canonical.com/blog/tag/server) [Support](https://canonical.com/blog/tag/support) [Ubuntu Advantage](https://canonical.com/blog/tag/ubuntu-advantage) [Ubuntu Advantage for infrastructure](https://canonical.com/blog/tag/ubuntu-advantage-for-infrastructure) --- Share the article A customer recently submitted a case that Pedro Principeza, a Canonical Support Engineer, was able to solve using an interesting technique. Principeza was contacted to help pinpoint the processes that were generating a high rate of I/O operations, affecting server performance. Implementing a trace to pinpoint workload usage was the best solution, however, resources on its set up were minimal. In order to formulate a thorough manner of tracking activity tied to two specific parts of the kernel, Principeza researched and dived into the Linux kernel official documentation. Principeza had experience with tracing capabilities and knew the next step would be simulating the problem locally on Linux. Once the behavior was simulated in Canonical’s lab environment, he was able to deliver the kernel tracing procedure in 30 minutes. After parsing through a lot of documentation, recreating the problem with Linux and tapping into previous experience utilising tracing capabilities, Principeza solved the case. The trace revealed that two applications, one security and one SDN-type application, were draining server resources. Upon detecting which applications were causing the high I/O rates, he engaged the applications’ support (outside Canonical) in order to fully understand the causes of the erratic behaviour to provide recommendations on reducing server consumption going forward. Tracking this type of resource usage requires a medium to high-level of expertise, so having additional engineering resources via technical support from experts like Principeza is a major value add to businesses working through complex IT issues. To provide guidance on similar cases in the future, the following articles are ***available to customers in our Knowledge Base\****: * [What Is The Jbd2 Thread?](https://support.canonical.com/ua/s/article/What-is-the-jbd2-thread) * [Tracing Filesystem Journaling Activity (Jbd2)](https://support.canonical.com/ua/s/article/Tracing-filesystem-journaling-activity-jbd2) If you are interested in learning more about Canonical’s support subscription, please visit [ubuntu.com/support](https://www.ubuntu.com/support) and feel free to [contact our team](https://www.ubuntu.com/support#get-in-touch) with any questions. *\*These links will not work unless you have a support account with Canonical. If you have questions about access to the Canonical Knowledge Base and support offerings, please* [*get in touch*](https://www.ubuntu.com/support#get-in-touch)*.* [Get in touch Interested in running Ubuntu in your organization?](https://ubuntu.com/about/contact-us/form) ## Sign up for our newsletter Get the latest Canonical news and updates in your inbox. Work email: \*I agree to receive information about Canonical's products and services. By submitting this form, I confirm that I have read and agree to [Canonical's Privacy Policy](https://canonical.com/legal/dataprivacy). Sign up ## Share on --- ## Related posts [### Tracing a memory leak bug in PID 1 and contributing an upstream fix: a Linux support story](https://canonical.com/blog/fixing-memory-bug) How Canonical Support helped a global retail organization trace the cause for an unusual memory leak originating in PID 1. By investigating the issue across three separate... [Lidia Luna Puerta](https://canonical.com/blog/author/lidia-luna) 17 July 2026 [### A decade of Ubuntu on IBM Z and IBM LinuxONE](https://canonical.com/blog/a-decade-of-ubuntu-on-ibm-z-and-ibm-linuxone) This year we celebrate a decade of Ubuntu Server support on the s390x architecture: marking a long-standing collaboration between Canonical and IBM that began at LinuxCon 2015.... [Pedro Lazzarotto](https://canonical.com/blog/author/pedro-lazzarotto) 12 June 2026 [### How Canonical Support solves hard Linux performance bugs  – even in 12-year old code](https://canonical.com/blog/support-solves-bugs-in-12-year-old-code) A 12-year-old bug in libnss-db caused getent enumeration to slow to a crawl – and showed how far expert support can go when a customer brings the right evidence and the right question. [Lidia Luna Puerta](https://canonical.com/blog/author/lidia-luna) 1 June 2026 [### When an upstream change broke smartcard FIPS authentication – and how we fixed it](https://canonical.com/blog/when-an-upstream-change-broke-smartcard-fips-authentication-and-how-we-fixed-it) This is the story of how Canonical’s Support team provided bug-fix support: we tracked down an upstream change in OpenSC that inadvertently broke FIPS compatibility,... [Lidia Luna Puerta](https://canonical.com/blog/author/lidia-luna) 12 February 2026