Re: reads vs writes

You need to be aware that this statistic might be absolutely irrelevant.

You might find that due to a bad design which might had been overlooked, like some missing Indexes or some bad execution plans or some incorrect partitioning strategies you have read far more data than required.

Similar, you might have a lot of useless Indexes and you write far more than required.

Lastly you might have some wrong interpretation of business rules which can influence this.

What matters is if you read and write effectively, meaning no more that you need. But this again it should be defined by some kpi in terms of how long something in your database should run.

Don't want to discourage you,but personally I find useless what you want to achieve.

On Mon, Feb 12, 2024, 22:00 Ram Raman <veeeraman_at_gmail.com> wrote:

> Hi all,
>
> We are trying to find out if our database is more read or write intensive.
> so I queried v$sysstat in our DB that has been running for the past 2
> years. When i was looking for physical writes, I queried for statistics
> using 'physical write%' and 'physical read%' and it looks like we are read
> heavy with about 15x more reads than writes. Is this a right way
> approximately to gauge if a system is read or write heavy?
>
> --
> Thanks,
> Ram
>
>
>

--
http://www.freelists.org/webpage/oracle-l