Vertical scaling implementation

In a vertical scaling implementation you maximize the number of client connections supported on a single host.

The key features of this implementation are:

  • The Service Manager system consists of several servlet container processes running on one physical host
  • The implementation allows administrators to specify a system connection limit
  • The Service Manager system can manage a number of concurrent client connections up to the number of servlet container processes times the threadsperprocess value (For example, 6 servlet container processes supporting 50 threadsperprocess can support up to 300 client connections)
  • The implementation allows administrators to specify the communication ports the system uses
  • A dedicated load balancer process manages and routes client connections to available servlet container processes
  • Administrators can dynamically add and remove Service Manager instances from a virtual group

A vertical scaling implementation is typically used in small to medium environments where hardware system resources are limited. A vertical scaling implementation can support as many client connections as the Service Manager host has available system resources.

You can convert a vertical scaling implementation into a horizontal scaling implementations with the addition of virtual grouping parameters and one or more additional servlet container instances installed on separate physical hosts.

Note: There can be only one kmupdate process running at any time regardless of the number of hosts. Starting more than one kmupdate process causes unpredictable behavior on the search engine server.

Related topics

Example: Setting up a vertical scaling implementation
Server implementation options
Startup options for servlet container processes

Related topics

Vertical scaling implementation diagram
Configuring a vertical scaling environment