RE: Slightly-OT: Throw HW at a SW/DB problem

  • From: "Amaral, Rui" <Rui.Amaral@xxxxxxxxxxxxxxxx>
  • To: "'andrew.kerber@xxxxxxxxx'" <andrew.kerber@xxxxxxxxx>, "rjoralist2@xxxxxxxxxxxxxxxxxxxxx" <rjoralist2@xxxxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 27 Jun 2011 11:06:54 -0400

Poke a stick in my eye if ever this becomes the norm. Irresponsible commentary 
from a seasoned "professional". Not mention the little gotcha about ssd's - 
write endurance - whether you consider it a FUD or reality - it's not something 
to take lightly.

________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Andrew Kerber
Sent: Monday, June 27, 2011 10:50 AM
To: rjoralist2@xxxxxxxxxxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Slightly-OT: Throw HW at a SW/DB problem

He forgets a basic rule of data (Murphy's law of databases):

Data will always expand to exceed the capacity of the available resources by at 
least 10%.



On Mon, Jun 27, 2011 at 9:45 AM, Rich Jesse 
<rjoralist2@xxxxxxxxxxxxxxxxxxxxx<mailto:rjoralist2@xxxxxxxxxxxxxxxxxxxxx>> 
wrote:
I think I'm gonna be sick:

http://www.sqlmag.com/article/Performancetuning/ssds-performance-tuning-experts-milkman-139591

This mentality **in a database professional** completely escapes me.  It
brings to mind that I just "upgraded" my Blackberry to one that has 2x the
CPU and 5x the RAM -- and still works just as bad as the one it replaced (if
not worse).

Anyone from the Oracle camp advocating/predicting hardware-based "tuning"?

Rant over.

Rich

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




--
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

NOTICE: Confidential message which may be privileged. Unauthorized 
use/disclosure prohibited. If received in error, please go to www.td.com/legal 
for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié. 
Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière 
d'aller au www.td.com/francais/avis_juridique pour des instructions.

Other related posts: