Home » RDBMS Server » Performance Tuning » Advanced Queuing correlation id (Oracle 10g Release 10.2.0.1.0)
Advanced Queuing correlation id [message #429187] Mon, 02 November 2009 08:09 Go to next message
johnbach
Messages: 32
Registered: June 2009
Member
I have a single QUEUE TABLE.
Will there be any considerable difference in performance(dequeue time) between these two scenario?
scenario 1:
7 Queues each with 1 million entries
scenario 2:
Only one queue,but have 7 different correlation id,each with 1 million entries.


Re: Advanced Queuing correlation id [message #429218 is a reply to message #429187] Mon, 02 November 2009 10:22 Go to previous messageGo to next message
Michel Cadot
Messages: 63804
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Only a benchmark and your treatments may answer this.
What is your idea to mix up all entries? Why do you want to do this?

Regards
Michel
Re: Advanced Queuing correlation id [message #429279 is a reply to message #429218] Tue, 03 November 2009 00:48 Go to previous message
johnbach
Messages: 32
Registered: June 2009
Member
Tested both scenario
Scenario 1
Faster even at 80 dequeue per second (~ 1 milli second per dequeue)
ENQUEUE
     qname:='pin_q_'||:new.amount;
      DBMS_AQ.enqueue(queue_name=>qname,

DEQUEUE
qname:='pin_q_'||iamount;
   DBMS_AQ.dequeue(queue_name=>qname,


Scenario 2
Slow (~ 700 milli second for dequeue)
ENQUEUE
l_message_properties.correlation:=:new.amount;
      DBMS_AQ.enqueue(queue_name=>'pin_q',

DEQUEUE
l_dequeue_options.correlation:=iamount;
    l_dequeue_options.navigation:=dbms_aq.FIRST_MESSAGE;
    DBMS_AQ.dequeue(queue_name=>'pin_q',
Previous Topic: BITMAP INDEX performance issue
Next Topic: undo usage in a query
Goto Forum:
  


Current Time: Mon Sep 26 19:39:18 CDT 2016

Total time taken to generate the page: 0.11505 seconds