The official catchy Oracle name is "Exalytics In-Memory Machine X2-4" which come to think of it is not very catchy but does sound techie. Larry Ellison announced Exalytics at OpenWorld 2011 to great fanfare and little details. In a nutshell, it's Essbase, OBIEE, and TimesTen running in-memory on a really powerful server. How powerful? 40 Intel cores (4 Intel Xeon E7-4800 processors with 10 cores each), a terabyte of RAM, an InfiniBand backbone (40 GB/s when talking to Exadata), two 10 GB/s ethernet ports for connecting to non-Exadata sources, and 3.6 TB of hard drive. Imagine Essbase running fully in memory with ethernet speeds so powerful it's like you're running Essbase locally (subject to the speed of your actual corporate network, of course).
It's an exciting development for those people who want to make BI virtually real-time. There's even a slightly modified front-end on the OBIEE side of things to make queries a more interactive "speed of thought" activity. If you want to make Essbase even faster, this is the solution for you. Early benchmarks have been all over the map (I've seen 5 times improvement all the way up to 80 times improvement) but suffice to say, that once you've tuned your Essbase cubes for running in-memory, you'll be looking at five-fold improvement at the bare minimum. If you want to learn more, Oracle has an in-depth whitepaper at:
Various rumors have leaked out on the pricing for Exalytics, but it's now been finalized and posted on the Oracle website. While there are a few places where you can find this on the web this morning (including the actual PDF of the pricing from Oracle), the best summary I've read comes from Chris Kanaracus at IDG.
Here are the pricing highlights:
- Hardware: $135,000
- Processor Licenses of TimesTen: $34,500
- Named User Licenses of TimesTen: $300
- Processor Licenses of BI Foundation Suite: $450,000
- Named User Licenses of BI Foundation Suite: $3,675
Some additional points:
- Annual Maintenance is the typical 22% of net.
- Licenses of TimesTen and BI Foundation Suite must be equal (if I'm reading a footnote on page 8 of the price list correctly).
- BI Foundation Suite includes Essbase, OBIEE, and Oracle Strategy & Scorecard Management. The pricing above is the current pricing for BI Foundation Suite (technology price list, page 5).
- Processors must be licensed for every core meaning full list at processor licensing for every core on the box is almost $20,000,000 (though the article points out that Oracle would probably drop that as much as 70%). That's still a lot of money so I foresee most companies going with the named user license.
- Oracle will probably discount named users as well. Assume ~50% discount on these (though Chris Kanaracus points out that it can go as much as 70% for large deals). Hardware, following Oracle traditional appliance discounting, will discount at most 25%.
Following the math, list price for 100 users (the minimum you're allowed to buy) would be about:
- Hardware: $135,000
- Software: $397,500
- List Total: $532,500
- Discount: $232,500 (25% hardware, 50% software)
- Net Total: $300,000
- Maintenance: $66,000 (due on signing for 1st year)
Before I leave the subject of Exalytics, I have to point out just how worried SAP is about Exalytics competing with their HANA solution. SAP's Sanjay Poonen (President, Corporate Officer of Global Solutions at SAP) wrote one of the worst attack pieces I've ever read right after Exalytics was announced. To summarize his point, Essbase is an old dying OLAP technology that's been around for 20 years and is therefore worthless. First of all Sanjay, the relational database has been around a lot longer than that and no one is saying that RDBMS' are going away. But my main problem with his article is that if you take him at face value, he has no idea about Essbase beyond 10 year old bad competitive intelligence information. To quote from his article he paid to post on Forbes.com:
Essbase even with all its “optimization” cannot efficiently run in-memory – you still have to do pre-calculations and pre-aggregates, with no ability to do calculations on the fly. You’d have to limit how far the Essbase calculations propagate to ensure performance doesn’t blow up, and insert operations force the indexes in the database to be rebuilt, thus ruining performance...
Um, not to imply that no one fact checked your essay Mr. Poonen, but you're talking about Essbase Block Storage (the 20 year old technology which most would think means it's more reliable than something released in the last 2 years). Essbase Aggregate Storage (created about 6 years ago) was created to solve all these problems. It's a fundamentally different architecture than Essbase block storage: it doesn't need to be aggregated, it doesn't need to be pre-calculated, and it does all formulas and calculations on the fly. There is no separate index that needs to be rebuilt. Basically, all your problems you're listing (forgetting that there are many things the Essbase Block Storage does better than any OLAP technology out there), are for the Essbase Block Storage technology.
I would forgive Sanjay Poonen for just using out-dated information under the excuse that he doesn't have access to Essbase directly, but a simple Google search takes you to the Essbase Wikipedia page where it defines Essbase Aggregate Storage:
Although block storage effectively minimizes storage requirements without impacting retrieval time, it has limitations in its treatment of aggregate data in large applications, motivating the introduction of a second storage engine, named Aggregate Storage Option (Essbase ASO) or more recently, Enterprise Analytics. This storage option makes the database behave much more similarly to OLAP databases like SQL Server Analysis Services. Following a data load, Essbase ASO does not store any aggregate values, but instead calculates them on demand.
That text has been on Essbase's Wikipedia page for a few years, so the only conclusion I can draw is that either Sanjay doesn't know how to use Google, or he was blatantly ignoring the facts. Assuming he's not a moron, SAP must be very afraid of Exalytics to put this piece together and hope no one pointed out how fundamentally errant the whole discussion is. I don't have time to point out every one of the wrong things in his article, but if you wish to comment on his article, visit here, and feel free to correct anything you disagree with.
And just in case Sanjay thinks I'm not willing to stand behind what I write, I challenge him to a cube build-off. Let's get together and put whatever cube technology SAP is pushing today (SAP BW? SAP BIW? Business Objects? HANA?) up against Essbase. You and I can jointly benchmark cube build time, query time, calculation time, whatever you want, and we'll both jointly publish the results. If you're not afraid of how the results will come out, call my office at 01-972-735-8716. Ask for Edward Roske and say it's Sanjay Poonen calling. I'll make sure my receptionist knows to forward your call to my cell anywhere I am in the world. I look forward to hearing from you.
When does Exalytics release?
Exalytics should be generally available soon, but it has to wait until, among other things, Essbase 184.108.40.206 comes out since they're tweaking Essbase to run better in-memory. If I had to guess, I'd say before the end of Oracle's fiscal year (May 2012). Exalytics will continue to make Oracle Essbase and OBIEE a factor to be reckoned with going forward. I'm told there's a waiting list for the first Exalytics boxes to come off the line, so call your Oracle rep now if you're interested.