Find content
), next are some questions.The ISVIEW file sent corresponds to a normal load for around 250 concurrent users but this does not mean an overload at all. In fact we have about 2 weeks every 4 months that are critical and presents slow downs due about 380 concurrent users and high process demand, at these moments we have observed more than 2500 files opened at once, this is reported by the corresponding ISVIEW file.
SL_SPIN was setted to such number for 2 reasons: 1) Was a Local Support recommendation and, 2) Was a result after large test sessions. So, we don´t find how to set this value in accordance our server configuration: number of processors & memory. Is there any documentation that help us to solve this ?
The SHMSIZE parameter is deducted by the other 4 parameters. Do you recommend to set this to a fixed value?
We use PRO-ISAM files for small size ones & C-ISAM files for larger than 1GB. Really Oracle is used since jan 2004, but is used for interface purposes.
We have constantly session tests to reproduce overloading, these runs pasts 10:00 PM. The first test runs with 350 concurrent users ending with a duration of 12 minutes, then we kill the ISCOLLECT processs without restart the server. The second test with the same number of users longs 5 minutes, can you tell me why this happens?
Can you tell us where to set the TRACEALL & TIMESTAMP parameters?
At this moment we are unable to upgrade our PRO-IV 4.6 version.
To kill the ISCOLLECT process, we log off all users then kill the process without restart the system. This task longs 1 to 2 minutes. These week we have done this process 5 times in working time.
Please, we need some feedback concerning to interpret correctly de ISVIEW file contents. Can you help us?
