Tuning steps in a v880 SUN box [message #61515] |
Fri, 30 April 2004 01:27 |
Shibaji Ghosh
Messages: 39 Registered: April 2002
|
Member |
|
|
Hello,
I have a SUN v880 box with 4 CPUs and 8GB RAM. I am running a ORACLE 9i instance. I intend to load 30 Gigs of data daily. It is behaving very slow. There are only one dbwr process in operation. The buffer cache size is around 3 Gigs. The log buffer is around 60Mb. There are 4 groups of Redo log files with 2 members in each. Size of each member is around 100Mb. The data will be loaded from flat file. There's one xml file where certain rules are set. This will parse the data and then store in the DB. This is how I tried to optimize :
1.> The tables where data will be loaded are placed in a separate tablespace (locally managed with uniform extent size of 100Mb)
2.> I am planning to change the number of DBWR processes to 4, since there are 4 CPUs involved. Will it aid in any performance improvements ? Are there any risks involved ? How much gain can I expect ?
3.> I am planning to drop the existing log files and create 3 log groups with 2 members in each. I intend to keep the log sizes to 1Gb for each member ? Am I going too much ? What do you recommend can be the size like ? Log files will not grow and there will be 6 GB of spaces stored for log writing.
4.> I am getting much log space request and although the buufer cache is around 3 GB, the hit ratio is around 81%. Is it a good figure or do I need to tune the buffer cache ?
This is from my side. Can anyone point me out the loopholes in my tuning intentions. Any more suggestions / parameter tuning are very much welcome.
Thanks in advance.
Shibaji
|
|
|
Re: Tuning steps in a v880 SUN box [message #61564 is a reply to message #61515] |
Wed, 05 May 2004 09:43 |
croca
Messages: 50 Registered: January 2004
|
Member |
|
|
What about loading data in direct mode?
If you are going to load data from flat files, indicates you are planing to use SQL*Loader, so, you can try DIRECT mode to load data, and, you can also try it in PARALLEL.
You can also try to set NOLOGGING to the tables you are loading into.
Best luck.
Yo.
www.otools.com.ar
|
|
|