Home » RDBMS Server » Performance Tuning » Optimal size for my memory components ( development db )
Optimal size for my memory components ( development db ) [message #236531] Thu, 10 May 2007 03:05 Go to next message
kesevan
Messages: 17
Registered: April 2007
Location: MUMABI
Junior Member


Dear Michael,

Iam providing the follwoing details for my development database ( ver: 9.2.0.0.0 ) :


our physical RAM size is : 1 GB.

Now i have been instructed to configure the SGA properly accordingly to the RAM size..and tune the enitre database..
the reported problem is some SQLs are running very slow... apart from that, need to set the necessary parameter
to appropriate size...



the following details are from v$parameter..
---------------------------------------------
sga_max_size - 403774644 ( 385 mb )
shared_pool_size - 201326592 ( 192 mb )
shared_pool_reserved_size - 10066329 ( 9.59 mb )
large_pool_size - 8388608 ( 8 mb )
java_pool_size - 33554432 ( 32 mb )


db_cache_size - 33554432 ( 32mb )

sort_area_size - 524288 ( 512 KB )
sort_area_retained_size - 0

db_file_multiblock_read_count - 128

session_cached_cursors - 0
cursor_sharing - EXACT
open_cursors - 500





please guide me to set the optmial size for shared pool and buffer cache.
we are using JAVA as front end application ( hence we have changed from default value 24mb -> 32mb )
is this ok ?

I have sent buffer cache advisory - ON.....
pls guide me to set the optimal size basically...then i see all the necessary parameters..like
curosr_sharing, session_cached_cursors....etc.... as this is development environment.

pls guide me
thank you
Re: Optimal size for my memory components ( development db ) [message #236533 is a reply to message #236531] Thu, 10 May 2007 03:13 Go to previous message
sriram717
Messages: 48
Registered: February 2007
Location: UNITED KINGDOM
Member
Hi,

There is no thumb rules defined on setting up these parameters.

You need to becnmark your application and then only arrive at an optimal value and this may need to be changed later on depending up on the data volume change as well the SQL statements/packages/procedures in your system.

Its better you do a benchmark of your application , collect statspack at regular intervals and then analyze it.This will give you the roadmap ahead.

Thanks
Previous Topic: Long Running SQL -V$session_longops
Next Topic: indexes difference as table columns
Goto Forum:
  


Current Time: Thu Dec 08 19:52:26 CST 2016

Total time taken to generate the page: 0.14916 seconds