System CPU at 100%

Hello Boomi fans !

I have a cool success story:

Some problems have been challenging us for some time

so I will share how we were able to fix them.

Sometimes the System CPU was used at ~ 100% (for 6 hours in the example below)

And most of the time the Delta CPU usage (difference between System and Boomi CPU usage) was high.

We managed to solve both of these problems by applying updates KB5011560 and KB5011564 on our Windows Server 2012 R2.

Here is the same load pattern few days later:

Monitoring our Boomi infrastructure helps us to:

Trust through transparency — Prevent fingerprinting between the infrastructure, operations and development teams. Good data makes the source of the problem much more obvious bringing these teams together at the round table of Monitoring.

Prevention — By collecting samples over time, we can detect abnormal load patterns and prevent outages.

Accurate performance tuning and testing — Monitoring data helps eliminate the guesswork from performance tuning and load testing.

Fact-based configuration changes — We can observes the system health over time. As a result, the effects of configuration changes are clear. With this feedback loop, the operation team is more confident when it performs configuration changes.

Detect excess resource consumption — Or, “Who ate Boomi’s pudding?". It is possible to identify parasitic resource consumption done by other system services installed on the same server.

We can also detect inefficient Boomi process designs by analyzing their load patterns.

Accurately forecast infrastructure requirements — Trend lines helps us to predict when we need to scale up our Boomi infrastructure capabilities before anything breaks.

With centralized visibility and oversight, support becomes predictable.

Reference:

Boomi Monitoring - Best Practices

Resources on Boomi