Why are Threadpool Workers Constrained by CPUs?
Last updated on AUGUST 18, 2017
Applies to:Oracle Financial Services Revenue Management and Billing - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The sizing guidance from Oracle documentation quotes approximately four threads per CPU as a guide. We are using 24 threads on 16 CPUs on a VM. When we increase to 30 threads the performance degrades and actually takes longer overall. Similarly on a physical server, using 12 CPUs, we use 24 threads. When we increase this to 30 threads it also degrades. This indicates that the threadpool workers are constrained by the CPUs and are not getting what is expected from each CPU. We seek advice on why this would be the case. For all these tests the CPUs are running high utilization of 85% or higher.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms