This article is about what inference to draw when a SharePlex process acquires high CPU. It is just about providing some food for thought about CPU usage by a process like SharePlex’ s
The following points are worth noting when considering high CPU usage by any process including SharePlex processes.
*It should not normally be of concern as this could be due to replication volume and SharePlex's processes grab the available CPU to meet its processing needs. By the same token, if the box does not have much activity besides replication, then SharePlex's processes can be expected to acquire an outsized CPU slice.
*If the box lacks CPU resources all the processes including SharePlex processes are starved of the CPU resources, then one may need to think about looking into adding more CPU resources to it or upgrade it.
*If the SharePlex processes needs to be tuned to make them more efficient and consequently use less CPU, this is fair approach.
*Taking away the CPU slice from the SharePlex process in question by any OS means (such as renice in Unix) may turn out to be counterproductive as it can slow down replication or result in other side effects.
*Rarely it may be due to a bug with the functioning of that SharePlex process, thereby resulting in high CPU usage. But that bug will be short lived so a bug causing this is a very remote possibility.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center