Exadata X3H2M2: A few thoughts
Sep 30, 2012 / By Marc Fielding
Tonight at Oracle OpenWorld, Oracle CEO Larry Ellison announced the latest Exadata release: X3. It sports a hardware refresh including a big expansion in RAM and flash storage capacity: 4TB and 22TB respectively on a full rack. That works out to 512
mbGB RAM on each database server and a bit over 1.5TB of flash on each storage server.
It’s being promoted as a hierarchical caching strategy, Exadata X3H2M2, where the most-frequently-used 4TB of data is in the database buffer cache, the next 22TB is in flash, and the least-used sits on disk.
Larry continued to explain how this approach was much better than “flash disk” storage because it could intelligently adapt to data usage patterns. This is where I disagree: there are pros and cons to both approaches.
A flash cache approach, as in Exadata X3H2M2 (yes it’s a mouthful; will George Lucas sue for stealing his robot branding?) has the advantage of not requiring data redundancy: since the master copy of the data is on a set of redundant disks, the caches don’t need the same level of redundancy, which makes more efficient use of flash capacity.
That having been said, flash caching implies that the entire dataset will not fit in cache, and that requests for data not in cache must still go to disk, with the associated performance penalties. And depending on usage patterns (ad-hoc querying being one of the worst offenders), this uncached data access volume could be significant.