-
Hi
We are implementing Oracle Parallel Server. It is a OLTP application. We are carrying out stress testing , the time taken for inserting records with 150 Concurrent(inserts) user is expected to take less than 2 seconds for each user session.
But it is taking 20+ seconds for some users.
We tried altering the tables by setting the freelists to 20,
initrans to 4,pctused to 40.Could anyone tell me what other parameter that can be set at the table level. The table contains 4 columns and one being Long datatype and others being varchar datatypes..
When we go live we expect the concurrent users to be around 350+..
thanx in Advance
Sriram
-
well try to check v$session_wait when the 150 inserts starts and see what events are each sssion waiting for, from there you might be able to tune better.
SELECT username "User", event "Event", state "Waiting state",
seconds_in_wait "Wait time/Sec"
FROM v$session_wait a, v$session b
WHERE a.sid=b.sid
AND b.type='USER'
ORDER BY 1;
-
Or run a b/estat.sql during the data load.
-
The following suggestions may help you:
1 Increase redo log file and log buffer size.
2 Ensure that checkpoint occurs once in 15 minutes.
3 Keep minimum number of indexes on the table.
4 Allocate big extent size for this table
5 Increase DML_LOCKS parameter in INIT.ORA file and bounce the database.
6 If the table uses SEQUENCE, increase the cache size.
7 If hardware level log files are mirrored as well as software level on RAID 1+0 disks, drop those files. Create the mirrored log files on non-mirrored disk.
PS. Parallel Server is suitable for distributing the application load to many CPUs, not suitable inserting rows in the same table. If 300 users are connecting into 2 machines and accesing the same table, there could be many waits because of the lock on data block. You can experiment by connecting all users through one CPU and collect the wait statistics, and compare this statistics with the statistics collected from 2 CPU (more).
[Edited by tamilselvan on 12-14-2000 at 03:03 PM]
