You might want to limit IBM Content Search Services resource consumption, for
example, to share resources with other critical applications that
are running on the same server. However, in some cases, limiting resource
consumption can reduce IBM Content Search Services performance.
Limiting memory consumption
You can configure
the maximal memory consumption of the IBM Content Search Services server by using the configuration
tool. If you adjust the heap memory consumption, you might need to
adjust other parameters such as the queue size. For more information,
see the "Heap memory consumption" section in Parameters that influence performance.
Limiting indexing CPU consumption
If
you are running search or other critical processes on the same server
that you are using for indexing, and CPU consumption on the indexing
server JVM instance is very high (almost 100%), search time could
be very slow and other critical processes might be responding slowly.
To limit indexing CPU consumption by the
IBM Content Search Services server JVM instance, do
one or more of the following actions:
- Reduce the number of preprocessing threads and indexer threads.
- On some platforms, you can reduce the maximum available CPU cores
or CPU cycles for IBM Content Search Services server
processes (typically Java™ and
Stellent processes) or for the user that is running these processes.
- In some environments, you can distribute applications to different
virtual machines (for example, LPARs or Linux virtual
machines). You can use this technique to reserve CPU cores for your
critical applications.
- Move critical processes to a different server or use a different IBM Content Search Services server for search.