RE: Early 11g Advanced Table Compression #'s

From: Powell, Mark D <mark.powell_at_eds.com>
Date: Fri, 17 Aug 2007 14:01:18 -0400
Message-ID: <D1DC33E67722D54A93F05F702C99E2A90136F97B@usahm208.amer.corp.eds.com>

LOL, good catch. Technically speaking probably yes, though considering what has happened to us after a couple of upgrades gambit may well fit, just not here.

Mark D Powell -- Phone (313) 592-5148

	From: Kerber, Andrew W. [mailto:Andrew.Kerber_at_umb.com] 
	Sent: Friday, August 17, 2007 1:53 PM
	To: Powell, Mark D; oracle-l
	Subject: RE: Early 11g Advanced Table Compression #'s
	
	

	Do you mean run the gamut (from beginning to end) rather than

run the gambit (gamble, risk)?

	-----Original Message-----
	From: oracle-l-bounce_at_freelists.org


[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Powell, Mark D

	Sent: Friday, August 17, 2007 12:01 PM
	To: oracle-l
	Subject: RE: Early 11g Advanced Table Compression #'s

	 

	We have an OLTP and insert select * where is often used.  Data

quantities of 10M are not uncommon for the size of the transaction data though most of our operations work on just a few rows at a time. Then again we do have a significant batch cycle where entire tables get processed usually using loops that commit after every row or every few rows. In many cases the commits are necessary because the same rows we are updating are needed in other concurrent transactions and in some cases the commit is just left over from the days when the size of the rollback segments needed to support a transaction had to be kept small (application over 12 years old now).

I think good set of tests would run the gambit from single row operations, small set operations, to large set operations, and to row by row processing of the entire table because all of this can exist in one real-world system.

Mark D Powell -- Phone (313) 592-5148

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Ghassan Salem

		Sent: Friday, August 17, 2007 10:47 AM
		To: rxsherm_at_interealm.com
		Cc: oracle-l
		Subject: Re: Early 11g Advanced Table Compression #'s

		Roby,
		what do you mean by 'bulk insert' and 'bulk update'?
		To simulate an OLTP, you can you a loop inserting a row

and commiting each time, as OLTP means simple small transactions.

Rgds

On 8/17/07, Roby Sherman <rxsherm_at_interealm.com> wrote:

Seems my mailer has cut off the apostrophe from the URL... It should be:

http://web.mac.com/tikimac/iWeb/silicon/Roby_Sherman/Oracle_Certifiable/ Entries/2007/8/16_11G_TABLE_COMPRESSION_-_Don%E2%80%99t_Believe_the_Hype .html

On Aug 17, 2007, at 7:14 AM, Roby Sherman wrote:

For anyone interested, I ran some very quick benchmarks on 11g's new Advanced Compression table option COMPRESS FOR ALL OPERATIONS that Oracle is claiming was "specifically written to create only the most 'minimal' of performance impacts in OLTP environments.

The results are here:

http://web.mac.com/tikimac/iWeb/silicon/Roby_Sherman/Oracle_Certifiable/ Entries/2007/8/16_11G_TABLE_COMPRESSION_-_Don't_Believe_the_Hype.html

I guess their definition of minimal and my definition of minimal must be different... Anyway, if you're interested in this feature, feel free to take a quick look!

--Roby

NOTICE: This electronic mail message and any attached files are confidential. The information is exclusively for the use of the individual or entity intended as the recipient. If you are not the intended recipient, any use, copying, printing, reviewing, retention, disclosure, distribution or forwarding of the message or any attached file is not authorized and is strictly prohibited. If you have received this electronic mail message in error, please advise the sender by reply electronic mail immediately and permanently delete the original transmission, any attachments and any copies of this message from your computer system. Thank you.

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Aug 17 2007 - 13:01:18 CDT