Re: Suspected Spam: Private RPC process(queue)
Title: RE: Suspected Spam: Private RPC process(queue) ** 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:arslist@ARSLIST.ORG] On Behalf Of Jarl Grøneng Sent: Monday, September 18, 2006 11:17 PM To: arslist@ARSLIST.ORG 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___
Re: Suspected Spam: Private RPC process(queue)
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: arslist@ARSLIST.ORG 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
Re: Suspected Spam: Private RPC process(queue)
Title: RE: Suspected Spam: Private RPC process(queue) ** Jarl: Correct. And DSO can take a toll on your server if it is processing a large number of transactions (follow the sun or two site work). Also, any large scale user, such as Mid-Tier should have its own private RPC socket and its own set of threads. In addition, you might want to retune the database as the number of sessions (under Oracle) changes and you may need more cache memory, sort area, etc. The number of sockets in use depends on your system. If you are supporting a small site, <100 users, you may not need to do anything. If you are supporting a large site, with multiple Mid-Tier servers, you may want to investigate using private RPC sockets for them as well as any program that takes a large amount of time to complete. This keeps the fast/list threads available for your local users on the Windows User Tool. James McKenzie -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jarl Grøneng Sent: Wednesday, September 20, 2006 1:44 AM To: arslist@ARSLIST.ORG Subject: Re: Suspected Spam: Private RPC process(queue) 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:arslist@ARSLIST.ORG] On Behalf Of Jarl Grøneng > Sent: Monday, September 18, 2006 11:17 PM > To: arslist@ARSLIST.ORG > 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 __20060125___This posting was submitted with HTML in it___
Re: Suspected Spam: Private RPC process(queue)
Still I does not see any incrase in performance with private queues to ie mid-tier. I can see the benefit for groping mid.tier to a queue. With DSO i may be, since Remedy says its singel threaded if you do not set up a prvate process for DSO. -- Jarl On 9/20/06, McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED]> wrote: ** Jarl: Correct. And DSO can take a toll on your server if it is processing a large number of transactions (follow the sun or two site work). Also, any large scale user, such as Mid-Tier should have its own private RPC socket and its own set of threads. In addition, you might want to retune the database as the number of sessions (under Oracle) changes and you may need more cache memory, sort area, etc. The number of sockets in use depends on your system. If you are supporting a small site, <100 users, you may not need to do anything. If you are supporting a large site, with multiple Mid-Tier servers, you may want to investigate using private RPC sockets for them as well as any program that takes a large amount of time to complete. This keeps the fast/list threads available for your local users on the Windows User Tool. James McKenzie -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jarl Grøneng Sent: Wednesday, September 20, 2006 1:44 AM To: arslist@ARSLIST.ORG Subject: Re: Suspected Spam: Private RPC process(queue) 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: arslist@ARSLIST.ORG > 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 __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
