Re: Has anyone done any scalability work on dbms_lock?

• Original Message -----

> On a light-weight test on 8.1.7.4 at 700MHz on W2000 -
>
> About 15,000 request/release per second
> if you are using an ID

sounds plenty good to me. Thanks a lot.

> Bear in mind that each request or release will hit the
> enqueue latch a couple of times, so you could get
> contention for the latch in the two high-speed options.

OK. Will look out for these just in case.

> Bottom line - for high-speed OLTP type of work, I
> don't think you will get away with more than a dozen
> request/release cycles per transaction.

Not a worry, it's a workflow app. A few users but not much load, a little volume. I just need to make sure a given sequence of operations is not undertaken by more than one user per group (one lock/group) and a table lock is way too heavy to do this. Forms 9i, so it's not easy to fudge it with a C exit and I don't like servlets. Much better if I can do the lot in PL/SQL.

Thanks again.
Cheers
Nuno Souto
nsouto_at_optusnet.com.au

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Nuno Souto
  INET: nsouto_at_optusnet.com.au

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
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).