Re: CPU and memory metrics for databases in Oracle RAC
Date: Thu, 25 Mar 2010 20:33:38 -0700 (PDT)
Message-ID: <738a6b18-d279-497b-b1c0-ccbbbe8b44e1_at_t34g2000prm.googlegroups.com>
May be I misunderstood the questions, but it seems that Statspack reports for each instance will give you good idea of the impact of 3- rd node.
Let's say you produce Statspack reports for Node#1 and Node#2 prior to creation of Node#3 and they show for CPU usage per day
Monday: Node#1: 35000 sec, Node#2: 37000 sec Tuesday: Node#1: 36000 sec, Node#2: 38000 sec Wednesday: Node#1: 34000 sec, Node#2: 33000 sec Monday: Node#1: 36000 sec, Node#2: 36000 sec Monday: Node#1: 39000 sec, Node#2: 38000 sec
From this you can conclude that:
1. Each node consumes approx 10 hours of CPU time per day 2. The workload is evenly distributed between nodes 3. The workload doesn't change much between weekdays
Let's say you installed 3-rd node and got something like that:
Monday: Node#1: 22000 sec, Node#2: 23000 sec, Node#3: 25000 sec (and similar for other days)
From this you can conclude that workload is evenly distributed between 3 nodes, total CPU usage by all nodes is still 20 hours per day.
Similar observations can be made for I/O and for number of executions for top SQL statements (assuming you are using bind variables). Let's say you have SQL statement with hash value 12345. Previously it was executed 1000 times per hour on both nodes, after addition of node#3 it gets executed 660 times per hour on each node. Received on Thu Mar 25 2010 - 22:33:38 CDT