cpu load

[Bill Hassell · Accepted solution]

That sounds quite normal. The reason they seem to hogging the CPU is that the Java threads are very short lived. top (and Glance and other tools) can't represent dozens of short lived processes in a meaningful way. During the measurement period, 1 second for instance, 10 processes are shown aas running on CPU 0, but really, each process ran for a very short time, then probably went into a wait state for a semaphore or poll signal.