Yes, if this is the default setup of DSO: "DSO typically runs as a single threaded process..."
I see thet there is a performance benefit. But my point of this was a general use of private processes -- Jarl On 9/19/06, McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED]> wrote:
** Jarl: Look at the DSO tuning tips and tricks for a reason to have a private queue. James McKenzie -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jarl Grøneng Sent: Monday, September 18, 2006 11:17 PM To: [email protected] Subject: Suspected Spam: Private RPC process(queue) What is the purpose configuring private RPC process(queue)? If you direct all api calls into 390620 and 390635 (fast and list), and let them handle all request with: first come, first serve. With a private process you still have to wait for the database to complete its operations, and with a good tunes fast/list process I does not see any huge performance benefit. Back in the old days(AR Server on UNIX) with one server process linked to one RPC process I can see the benefit. -- Jarl _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
