Upper limit on T30FILE
Posted: Fri Dec 02, 2005 4:27 pm
There is no upper limit on T30FILE explicitly.
All of the structures sized within uvconfig must fit into a shared memory segment (sized by shmmax kernel parameter).
T30FILE sets the maximum number of slots (rows) in a table of open dynamic hashed file information in memory. This table can be viewed using the $DSHOME/bin/analyze.shm -d command. Each new row takes 114 bytes. Increasing this to 2000 means that you can have 2000 dynamic hashed files simultaneously open system-wide.
When you regenerate the shared memory segement (uvregen) you get a report about the size required. If that's nowhere near shmmax, then you have some headroom.
All of the structures sized within uvconfig must fit into a shared memory segment (sized by shmmax kernel parameter).
T30FILE sets the maximum number of slots (rows) in a table of open dynamic hashed file information in memory. This table can be viewed using the $DSHOME/bin/analyze.shm -d command. Each new row takes 114 bytes. Increasing this to 2000 means that you can have 2000 dynamic hashed files simultaneously open system-wide.
When you regenerate the shared memory segement (uvregen) you get a report about the size required. If that's nowhere near shmmax, then you have some headroom.