Re: 3GB RAM usage by Oracle

"Richard Foote"

> No, there's a third solution that's actually used by most shops.
>
> Have a DBA who actually knows *how* to tune a database and allocate memory
> *appropriately*. Requiring AWE is rarely required and suggesting that memory
> should simply be used because it's there, especially with the *significant
> overheads* that AWE entails is poor advice even by your standards.

Believe it or not, most USA shops already have tuned their SQL and their high physical I/O is due to not enough data cache. Things must be different where you live.

Besides, it's now easy with v$db_cache_advice and 10g AMM to see the marginal benefit of adding RAM. Are you suggesting that AMM recommendations are nonsense?

It's not uncommon to see working sets of frequently-referenced data of for than 30-gig for a large database. AWE is a great techniques for 32-bit Windows databases and I do it for dozens of databases every year, ALWAYS with great results.

Also, you ignore the economic reality of database tuning. Time and time again, it's too costly (in both time and money) for a shop to tune their SQL. It's also an admission that the IT manager hired goofballs (usually a non-US provider) to write the original code. Like I said, I have no problem throwing hardware at crappy code when the client doesn't want to tune it. Received on Fri Aug 27 2004 - 19:27:44 CDT