Before you start tuning, you would need the following information ..
1.) What is the number of concurrent sessions on the system at any point of time ?
2.) What is the JVM Max heap size value set ?
3.) Are you using the gateway or is it an open portal ?
4.) size of your desktop, number of channels etc.
5.) What is your hardware configuration, number of cpu's/ram etc ..
6.) have you done any prior performance tuning ?
7.) do you see any potential thread dead logs
when the system slows down do a ps -eLf | grep pid on the process id, it should list details abt the process like the number of threads open and the duration of each thread open and percentage of cpu used by each thread.
mpstat 5 pid should also list cpu usage information inaddition to smtx information.
Atleast you might also wanna run top to determine amount of memory used in addition to just cpu usage.
All these details could potentially tell you whats going on with ur system and you could appropriately tune based on that information.
HTH ..
web server / high cpu ?
if you truss the web server process what is it doing ?
- i have a number of problems in the past strangely
they were related to logging; it has problems handling
large log files - especially with debug enabled.
is debug enabled ? what is the log level ?
are the debug files showing anything ...
Hi,
Current configuration: solaris 8, 2 cpus, 1GB memory.
Portal running secure portal mode ie. with gateway
Answer to your questions
1) about 140 concurrent sessions
2) 805306368
3) gateway mode
4) no channels defined. redirect to a static customised page
5) 1 GB, 2 CPUs
6) follow what is recommended in the sp4
7) I have not tried this.
Some other parameters that you should consider ...
* is the auth module being used a custom auth module ?
* Check whether your script (depending on the stress tool being used) is ensuring that the users
are logged out properly if any errors are detected during a user cycle and not aborting that session leaving it to time out by itself. This could lead to more concurrent sessions even though the load tool does not reflect it. You can check the number of existing sessions through the admin console.
* Is your debugging turned on (platform debuging as well as the console debugging) ?
Satish