Monday, July 27, 2015

Will offlloading work for OLTP-compressed tables ?


If you create OLTP- or BASIC-compressed table and run count(*) on it using
cell_offload_processing = TRUE or FALSE
there is no difference in time between runs.

If you look to this query via OEM 12c it shows no offloading in SQL Monitoring page.
But if you add WHERE clause to your query, then SQL Monitoring will show offloading and query's time become much less.

Latest documentation of June 2015 talk foggy about BASIC and OLTP compression:


" Predicate evaluation is not offloaded to Oracle Exadata Storage Server in the following cases:

 "
 Oracle® Exadata Storage Server Software User's Guide
12c Release 1 (12.1)
E50471-14, page 7-58

I completely don't understand should offloading work for Basic ans OLTP compressed tables or not.

So we did the research.
As you know, the offloading (smart scan) has 3 sides:
- Projection (return only selected columns)
- Filtering (return only rows according WHERE clause)
- Storage Index (exclude some extents from IO)

And our results are:
------------ ---------- --------- ------------
Table Type  Projection Filtering Storage Index
------------ ---------- --------- ------------
No Compress      +        +          +
Basic            -        +          +
OLTP             -        +          +
HCC              +        +          +
------------ ---------- --------- ------------

No comments:

Post a Comment

Exadata account locked, pam_tally2 and host_access_control

Exam accounts are set up so that they are blocked for 10 minutes after the first wrong password entered. This brings a lot of inconvenien...