From the article:
Flash storage is known for enabling significant improvements in data processing operation speeds, allowing multi-terabyte databases to be stored "in-memory", with a read/write speed that is four times greater than HDD.
It's funny how good people think that is. It's actually not that good. When we moved from an older machine to a new one and we also moved from spinning disks on the SAN to a full-up SSD SAN, we only saw a 2X performance improvement and only on a few batch jobs. In most cases, there was no improvement.
I wasn't disappointed... it was actually better than I expected because I actually expected to see no improvement on anything. Everyone else was thinking that it was going to make a lot larger difference.
The problem is that code is what it is. It's either good code or it's not and, if it's not, things like SSDs aren't going to make much of a difference.
Heh... oh yeah. I've seen people do handsprings because some of their 8-10 hour jobs now run in 4-5 hours. Not really a "big" win from what I can see, though... especially since ever increasing scale will eat that meager gain up in a whole lot less time that people expect.
Don't get me wrong... I'll never turn down better hardware (especially network hardware)... but that's not where true performance gains are to be had. Even moving to MPP appliances will only give you up to 30X and that requires a fair bit of code rewriting to be able to use MPP.
If you really want performance of your code, there's really only one place to find it... in the code. 2-4 times and even 30 times faster is a paltry gain compared to what you can usually do in the code even on some relatively bad databases designs.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems
Create a Tally Function (fnTally)