Making the Most of Exadata

Posted in: Technical Track

My article Making the Most of Oracle Exadata in the August 2010 issue of the NoCOUG Journal has come out. It covers Exadata’s feature set, and then dives deeper, discussing how to make the best use of its capabilities. For those of you not subscribers of the print edition, it’s also available electronically.

I’m also going to be presenting a webinar about Exadata this coming Wednesday, August 11, and speaking about Exadata at Oracle OpenWorld in September.

Interested in working with Marc? Schedule a tech call.

About the Author

Marc is a passionate and creative problem solver, drawing on deep understanding of the full enterprise application stack to identify the root cause of problems and to deploy sustainable solutions. Marc has a strong background in performance tuning and high availability, developing many of the tools and processes used to monitor and manage critical production databases at Pythian. He is proud to be the very first DataStax Platinum Certified Administrator for Apache Cassandra.

7 Comments. Leave new

Just a point of clarification with recommended setting of CELL_PARTITION_LARGE_EXTENTS=TRUE: this parameter applies only partitioned tables, but does not change the extent allocation for non-partitioned tables.  Given that the default and recommended extent management is AUTOALLOCATE, there really is no need worry about 8MB extents for small non-partitioned tables since CELL_PARTITION_LARGE_EXTENTS? does not apply to them.  Manually setting INITIAL (to 8MB or larger) for large non-partitioned tables may be desirable though.

Reply
Marc Fielding
August 8, 2010 4:33 pm

Hi Greg,

You’re entirely right: CELL_PARTITION_LARGE_EXTENTS applies only to partitioned tables. I’ve run into the issue of small initial extents mostly in heavily partitioned tables due to the large number of segments, but it can happen on any table.

And as you point out, manually setting 8m INITIAL extent size is the workaround for non-partitioned tables, assuming the tables are large enough to use them.

Marc

Reply

@Marc

If you’ve run into an “issue of small initial extents mostly in heavily partitioned tables due to the large number of segments”, then you didn’t set CELL_PARTITION_LARGE_EXTENTS=TRUE, did you as this is exactly what this parameter setting adresses.

Your article says to use CELL_PARTITION_LARGE_EXTENTS, but it does not mention that in order to get 8MB INITIAL it must be TRUE or ALWAYS. TRUE is the recommended setting.

Reply
Exadata « Oracle Scratchpad
November 21, 2010 2:27 pm

[…] Making the most of Exadata […]

Reply
Making the Most of Oracle Exadata – A Technical Review | Structured Data
January 11, 2011 2:03 pm

[…] many of the key points of Exadata, however, even though I read (skimmed is a much better word) and briefly commented on the article back in August, after further review I found some technical inaccuracies with this […]

Reply
Making the Most of Exadata, revisited | The Pythian Blog
February 1, 2011 5:33 pm

[…] real-world performance group posted a technical review of an article I wrote last summer, entitled Making the Most of Oracle Exadata. I have a few comments on the technical concerns Greg […]

Reply
Making the Most of Exadata, revisited | Singer Wang
February 3, 2011 9:22 pm

[…] real-world performance group posted a technical review of an article I wrote last summer, entitled Making the Most of Oracle Exadata. I have a few comments on the technical concerns Greg […]

Reply

Leave a Reply

Your email address will not be published. Required fields are marked *