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

From: Amaral, Rui <>
Date: Mon, 27 Jun 2011 12:45:55 -0400
Message-ID: <1B861F1ABE40A84AA92AD585B20C558B2779CDFBCB_at_EX7T2-CV06.TDBFG.COM>

Stephane hit on the head. Bad code will always trump the HW not matter what. And there's lots of it. Case in point for me was playing with some ssd - reads were great as long as it was full table scans or very simple joins but when we got into multi-joins and complex queries that's where we got into the real work - and HW can't help you with that.

From: [] On Behalf Of Stephane Faroult Sent: Monday, June 27, 2011 11:06 AM
Subject: Re: Slightly-OT: Throw HW at a SW/DB problem

On 06/27/2011 04:45 PM, Rich Jesse wrote:

I think I'm gonna be sick:

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.




  Never underestimate bad developers. They can beat hardware anytime.

And to put some balm on your wounds, I have recently posted this on Youtube - partly as an answer to the (very well done by the way) Oracle Exadata video.

Don't read me wrong: there are obviously cases when powerful hardware, Exadata, SSD, you name it, is required. But well, not THAT often. At least, not as often as hardware providers pretend.

Reminds me of an application I have audited that was taking I think 1h15 to generate a 70 page report (on a reasonably sized Sun server). The vendor's answer was "upgrade the hardware". However, the rep made a big mistake: he run the app on his own laptop and it actually run faster. It made the customer suspicious. As it was a canned app, I switched a 10046 trace - couldn't edit the .trc and I had to grep my way into it. 600,000 queries in the trace file.

Try to beat this with hardware.

Stephane Faroult
RoughSea Ltd<>
RoughSea Channel on Youtube<>

NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to 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 pour des instructions.

-- Received on Mon Jun 27 2011 - 11:45:55 CDT

Original text of this message