Re: 3GB RAM usage by Oracle

On 24 Aug 2004 16:19:58 -0700, don_at_burleson.cc (Don Burleson) wrote:

>I've increased the RAM on over dozens of 32-bit dedicated Oracle
>Windows servers (most come with 8-gig RAM these days), and I've yet
>to see a 32-bit Oracle Windows server that did not benefit from using
>the wasted RAM. Almost all have "db file" waits as the top-2 timed
>events.
>
>In most cases using 4GT or AWE can half the disk I/O and greatly
>improve response time. Of course, you must allow for the HWM of PGA
>usage, but that's easily computed and you can use-it-all and avoid OS
>paging.
>
>Do you have a different experience?

I don't think your 'method' should be labeled 'tuning'. It should be labeled what it is: 'symptom fighting'. Hence, it will work for only a limited period of time, after which the poor customers have to hire you again to perform the same little trick. We have had cases were the entire database was 150 Mb in size, the cache was 1G and guess what? It still does't work. Unscaleable applications are unscaleable applications. The application needs to be fixed, NOT the hardware. If the unscaleable app runs on an unscaleable O/S like Windows, even worse.

What is if even worse: because of your little 'method', the developers responsible for creating the messes you claim to 'tune', will never learn how to do it properly.
You might even trap people to believe your 'method' actually works. You have been proven wrong in this group over and over and over again, and still you stick to promote symptom fighting.' Apart for keeping you employed, what is the big advantage of trying to persuade people to use a 'method' of which you know it doesn't work?

--
Sybrand Bakker, Senior Oracle DBA