Re: Workload Write vs. Read Ratio
- From: Martin Berger <martin.a.berger@xxxxxxxxx>
- To: postora@xxxxxxxxx
- Date: Sat, 19 Nov 2011 17:08:15 +0100
Andrew,
I read your email like this:
* you want to know the charateristics of your applications workload
* you collect some metrics
* now you somehow mistrust your data as you know there is more you can
measure out there?
just give it a try: try if you find a good correlation between the
workload and the metrics you collected. (Excel is fine in doing so)
If the correlation is good, you are lucky. otherwise you have to find
more/other metrics.
that's not the best answer, but hopefully a start
Martin
On Fri, Nov 18, 2011 at 22:16, Steven Andrew <postora@xxxxxxxxx> wrote:
> All,
> I have this little thing nagging me for a while and would like to get
> opionion from others. For capacity planning excercies, we generally
> monitor the metric 'physical read total IO requests' and 'physical write
> total IO requests' over a period of time to get IOPS. I see that Read
> requests to be around 200 and Write request around 2000. Does this mean the
> application workload is write intensive with write vs. read ratio of 90:10.
> What about all the caching that's done at the SGA for reads, likewise SAN
> caching for write. Shouldn't that be accounted as well when it comes to
> knowing the workload pattern of the application. How would you go about in
> knowing the workload ratio for an existing system.
>
> TIA,
> Andrew.
>
>
> --
> //www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
