Same topic (ADSM bottlenecks on NT), but a new variation......


About 2 months ago I wrote to the list asking about how many disk pools
could I create on an NT system ("NT and defining disk storage pool
volumes").

Further information has now come to light about this issue, and I was
wondering if IBM / Tivoli could define a hot fix to get around the problem??

Operating Systems use memory to control various aspects of the system. The
bit of memory that Windows NT 4.x uses to handle open files (Paged Pool) is
physically limited to 192 MB. "Larger" files are buffered into this area at
a rate of 1 MB memory per 1 GB file size.
This limits the sizes of open files on an NT system to 192 GBytes. Note:
Databases (Oracle, SQL, Exchange) do not open the whole database file at
once, so they do not meet the limits in the same way.

Currently (3.1.2.20) ADSM opens all the disk cache files when the server
starts up. Therefore no more than 150 GByte (approximately, as other files
are open as well) of disk cache can be specified on NT.


Question: Is it possible to modify the disk caches to be multiple smaller
files (say 40 x 5GByte, rather than 6 x 30 GByte), and to have ADSM open and
close these smaller files as it needs them, rather than opening all of the
files at ADSM server start up??


Cheers, Chris Jordan