Update, July 9, 2010: Pythian has now announced our range of services for Oracle Exadata, along with successful implementations and reference customers.
Notice to readers:
This is an excerpt of my liveblogging of the Keynote where the Exadata Storage Server was announced.
It is a mix of my comments in real time, and my quotes from things Larry Ellison said that I felt were worthy of mention.
You may be interested in reading more about Oracle’s Exadata platform. I would suggest taking a gander at Oracle’s product page and also reading up on Christo Kutrovsky’s Analysis of the Exadata and Oracle Database Machine announcement from a different point of view.
You may also be interested in the complete liveblog transcript of the keynote which includes my liveblogging of the rather boring HP advertiseynote before the big show.
I also separated out the Oracle Database Machine liveblog if you just want to get to the rest of the juicy stuff.
So here goes with the liveblogging transcript:
Announcing Oracle’s first ever hardware product.
The exadata programmable storage server.
Building intelligence into the storage server.
Allows us to reduce the amount of data.
Confirming HP is the partner.
Storage server does not pass disk blocks back to the database server, it actually passes query results.
Note: A few startups are doing this sort of thing already. They should be totally freaking out right now.
Slide explaining how query processing works in traditional storage.
Stark contrast to a grid of exadata storage servers, with processing ability local to each and every disk drive.
“We actually pass the query from the database server directly into the storage servers.”
Explaining how this works.
This reminds me hugely of kickfire for mysql, but for Oracle.
Cool, they’re provisioning two infiniband pipes per storage server. Nice. 40gbps.
Marc Fielding: “The problem is still the disk drives.”
Larry: 1gb/s per exadata storage server, you can have dozens working in parallel.
Christo: 1gb/s??? that’s not that good.
Immediately available for Linux., will work with any Oracle database.
Available for x86. Christo: “not 64 bit???????”
By the way, I made a bet with Paul Cunningham that Kickfire would fail because of Moore’s law. I wonder if I should bet against this tech too.
More details to come…
Learn more about Pythian’s services for evaluation, migration to and operational support for Oracle Exadata.
Paul, do you have more comments on the kickfire thing? I can’t understand that very well.
By the way, I made a bit with Paul Cunningham that Kickfire would fail because of Mooreâ€™s law.
thanks for passing on the news, much appreciated.
Just wondering about this:
“By the way, I made a bit with Paul Cunningham that Kickfire would fail because of Mooreâ€™s law.”
Maybe it’s ignorance on my part, but I don’t see what you mean. Genuinly interested, can you pls. explain? TIA,
Thanks for the mention of Kickfire. On the question of Kickfire vs Moore’s Law I would point your readers’ to a blog posting we did on the topic: https://www.kickfire.com/blog/?p=19. In essence, the Kickfire chip architecture is based on dataflow, not instruction-flow. The dataflow architecture is fundamentally more efficient for large data volume processing. This is why, as has happened in other industries before, once the transition to dataflow has been made it is next to impossible for general-purpose CPUs to catch up. This is why Nvidia still leads in graphics, not Intel, and why Juniper and Cisco use specialized routing chips not processors from Intel or AMD.
Btw, Oracle’s Exadata server is much more akin to Netezza than to Kickfire. Both use hardware to filter from disk to memory. In both cases though SQL is still executed on general-purpose CPUs, not on a SQL chip.