Show Posts
1
Documentation / TSM Connection Pooling Introduced with 8.5.0.6
« on: March 26, 2013, 03:59:34 PM »
As of 3/26/2013, this is an undocumented feature. Be aware the feature is turned on by default. Via a PMR, IBM provided the following response:
CMOD connection pooling logic
CMOD recently implemented a form of connection pooling for TSM. It is available in CMOD versions 8.5.0.6+ and 9.0.0.0+.
Up to 100 concurrent sessions total per CMOD library or object server
Short-lived connections (15 idle seconds)
Once the maximum CMOD connections are in use, new connections are added by closing the oldest current connection when it goes idle and adding a new connection to the pool
Prior to implementing connection pooling CMOD would perform one function per connection. For example, to retrieve an object, CMOD would open a connection to TSM, query for the object, retrieve it if found, and close the connection. For a CMOD system which is not under load, this is still the behavior.
However, for systems under load, if TSM requests are coming in faster than 1 every 15 seconds, then the connection pooling will start to be noticed in that the connection to TSM will no longer be closed after the function is completed and be reused if idle. Otherwise multiple simultaneous connections will be created.
The reason these connections are short-lived is to prevent media contention on the TSM server. We noticed during testing that keeping the connections open permanently caused volumes to be locked until the volume timeout. Since the minimum volume idle dismount time is 1 minute, this proved unacceptable in load testing.
CMOD connection pooling logic
CMOD recently implemented a form of connection pooling for TSM. It is available in CMOD versions 8.5.0.6+ and 9.0.0.0+.
Up to 100 concurrent sessions total per CMOD library or object server
Short-lived connections (15 idle seconds)
Once the maximum CMOD connections are in use, new connections are added by closing the oldest current connection when it goes idle and adding a new connection to the pool
Prior to implementing connection pooling CMOD would perform one function per connection. For example, to retrieve an object, CMOD would open a connection to TSM, query for the object, retrieve it if found, and close the connection. For a CMOD system which is not under load, this is still the behavior.
However, for systems under load, if TSM requests are coming in faster than 1 every 15 seconds, then the connection pooling will start to be noticed in that the connection to TSM will no longer be closed after the function is completed and be reused if idle. Otherwise multiple simultaneous connections will be created.
The reason these connections are short-lived is to prevent media contention on the TSM server. We noticed during testing that keeping the connections open permanently caused volumes to be locked until the volume timeout. Since the minimum volume idle dismount time is 1 minute, this proved unacceptable in load testing.
Perhaps this is what OP is looking for...