See my comments below
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Carey Matthew Black
Sent: Wednesday, September 20, 2006 7:35 AM
To: arslist@ARSLIST.ORG
Subject: Re: Private RPC process(queue)
See below...
My understanding of a private RPC queue is that it does the function of a Fast AND List operations as needed by the Client API calls that are routed to it. So the question becomes the how the volume of threads in the private queue and the volume of client API calls made to those threads. (and the length of time each call takes too.)
The real point however, is that a user of a private queue only has to "wait" on other users of that private queue.
..Exactly.
So if you write a single threaded API client and connect to a private queue (from one and only one client program at a time.) then you only need a single threaded private queue and your client will NEVER be waiting for anyone else API calls to finish before it's calls can be processed. (one lane of traffic with only one car in the line)
If you write a 3 threaded API client then you can connect to a three threaded private queue (from one and only one client program at a
time) then your client will NEVER be waiting for anyone else API calls to finish before it's calls can be processed. (three lanes of traffic with only three car in the lines)
If however you do not specify a private queue then all of the clients request "fight" for access to a Fast or List thread as they become available. If some other client usage spikes [ Like one DUMB user doing unqualified searches, click stop search, redo unqualified search and repeat a few dozen times in a row] then the other clients waiting for those same lanes of traffic (shared threads) get to wait for the RDBMS to answer the multiple unqualified searches that the user is not even waiting on anymore!
Yes if users start using private queues (when they should not be) then they could cause your private queue users the same issues. But few users ever try to mess around with such matters. To my knowledge there is no way to restrict users (in the ARS permission model) to being able to only use a private queue or not being able to use a private queue. Which sounds like an enhancement idea for "Disable-Client-Operation" (or something like that.)
..+1 on this. No client should be able to change the thread queue as an ordinary user from within the User tool.
James McKenzie
L-3 GSI
