Lock table table_name in exclusive mode - Performance gain?

Anyone do any bench marking, know of any papers, or using "lock table table_name in exclusive mode" to get a performance boost.

I'm trying to figure out how to do 90,000,000 operations
(add/change/delete) on the same table/partitions in a 4 hour period, and it
looks like lighting will have to strike twice in the same place for it to happen.

Any other suggestions on how to cut down on the cost of a transaction. I know about dropping indexes, using hash keys, partitions, unrecoverable, multi-process/threading, sql loader direct, and noarchivelog.

Help Meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: 
  INET: Brian_P_MacLean_at_eFunds.Com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).