faz

I have now switched to

SL_SPIN=1
SL_NAP=1

which is not the recommended setting for multiprocessor systems, but the system has been stable with these settings for 2 weeks now. I did not suffer any performance degradation by doing this.

faz

Thanks for your replies.

Let me go into further details, without mentioning the application.

1) regarding the operating system:
We use Solaris EIS Standard, 5.8 Generic_108528-23 sun4u sparc SUNW,Sun-Fire on all machines.
All systems come from a common jumpstart installation source and were installed within the last few weeks.

2) User Level
If the problem appears at night (the only time I can do some testing anyway) I have hardly any
user mode. If I shutdown the application and leave oracle up, the system is 99% idle. If the proIV app
is running, I have, for exampe 2%idle, 8%user,90% kernel, 0% iowait.

at this moment the application should be running a simple batch job that runs on one cpu.

3,4) I have about 120 .pro files, the file table in isview is 32 long. the output of isview is about 1000 lines
long, that is if I allow write access to the .pro files which normally is the case.

5) I do not have an isamlog, but I have created one now. I have seen the shared memory segment extend once,
I thereafter increased it.

6) isview seems not to be blocking on my system.

ever since we are using spinlocks, the proability of one out of mind task in the applikation slowing the entire system down seems to have increased. the application consists of over a hundred tasks, most of which I cannot restart seperatly.
I have browsed through the proIV docs on the website to see if there was was a bugfix related to this in any of the later releases, but I could not find anything.

faz