They wanted performance and went *RAID 5*? That pretty much sums the entire approach up. Let's not optimise the application first, the database second, but instead hide the problem by throwing hardware at it. Then what we'll do is use a RAID configuration that hobbles the write performance of the arrays and lets not mention what happens to performance when we lose a disk (don't say it won't happen).
Sure, RAID 5 is the answer to somethings, but not when the question is database *PERFORMANCE*.
Also - latency is more important than IOP/s. I don't care how many IOP/s you can do, if you're latency is high, the performance won't be. Most garden variety storage engineers don't seem to grasp this concept.
Wow Deja Vu. I remember the xBase (dBase / Clipper etc) languages being touted as the programming solution for non programmers. Programmers would be out of jobs, everyone would be writing their own applications. My first programming job when I left University was writing business applications in Clipper.
I wish I had stopped there. I read up until book 7 or maybe 9. The one where absolutely nothing happens and Rand has less than one chapter in the entire book.
1) Find a small company on the stock exchange 2) Buy some shares in it for a low price 3) Post a story on Slashdot with the company name and 'Google' in the same sentence 4) Watch the stock price go through the roof 5) Profit
I use google many times a day. I can't see this graphing tool becoming as ubiqituous as Google. I can't see that company name entering the English language as a verb like google.
Can you pay to get your story on Slashdot these days? This seems more like advertising. It certainly isn't interesting news.
I hope they don't need to use the pow() function on Yahoo. It's been broken in every release from 4.1.2 to 4.2.3. Sure, they fix the bugs, but never actually put the bug fix out. Maybe, just maybe, we will have a working version of the pow() function in 4.3.0
Slashdot Mirror
They wanted performance and went *RAID 5*? That pretty much sums the entire approach up. Let's not optimise the application first, the database second, but instead hide the problem by throwing hardware at it. Then what we'll do is use a RAID configuration that hobbles the write performance of the arrays and lets not mention what happens to performance when we lose a disk (don't say it won't happen).
Sure, RAID 5 is the answer to somethings, but not when the question is database *PERFORMANCE*.
Also - latency is more important than IOP/s. I don't care how many IOP/s you can do, if you're latency is high, the performance won't be. Most garden variety storage engineers don't seem to grasp this concept.
I heard it was going to ship with a pre-installed copy of Duke Nukem Forever.
Wow Deja Vu.
I remember the xBase (dBase / Clipper etc) languages being touted as the programming solution for non programmers. Programmers would be out of jobs, everyone would be writing their own applications. My first programming job when I left University was writing business applications in Clipper.
I predict ChromeOS will be as successful as Microsoft Bob.
I wish I had stopped there. I read up until book 7 or maybe 9. The one where absolutely nothing happens and Rand has less than one chapter in the entire book.
Here's an idea:
1) Find a small company on the stock exchange
2) Buy some shares in it for a low price
3) Post a story on Slashdot with the company name and 'Google' in the same sentence
4) Watch the stock price go through the roof
5) Profit
I use google many times a day. I can't see this graphing tool becoming as ubiqituous as Google. I can't see that company name entering the English language as a verb like google.
Can you pay to get your story on Slashdot these days? This seems more like advertising. It certainly isn't interesting news.
I hope they don't need to use the pow() function on Yahoo. It's been broken in every release from 4.1.2 to 4.2.3. Sure, they fix the bugs, but never actually put the bug fix out. Maybe, just maybe, we will have a working version of the pow() function in 4.3.0