Table of ContentsView in Frames

Benefits of concurrent HTTP sessions

You must keep multiple TCP/IP connections to the StorageGRID Webscale system open to allow idle sessions to perform transactions as required. The number of client applications also affects how you handle multiple TCP/IP connections.

Concurrent HTTP sessions provide the following benefits:

Client applications should establish multiple HTTP sessions, either on a client-by-client basis or on a session-pool basis. When a client application has to perform a transaction, it can select and immediately use any established session that is not currently processing a transaction.

Each StorageGRID Webscale system's topology has different peak throughput for concurrent transactions and sessions before performance begins to degrade. Peak throughput depends on factors such as computing resources, network resources, storage resources, and WAN links. The number of servers and services and the number of applications that the StorageGRID Webscale system supports are also factors.

StorageGRID Webscale systems often support multiple client applications. You should keep this in mind when you determine the maximum number of concurrent sessions used by a client application. If the client application consists of multiple software entities that each establish sessions to the StorageGRID Webscale system, you should add up all the sessions across the entities. You might have to adjust the maximum number of concurrent sessions in the following situations: