Thanks for the information. Andrew.
On Wed, Apr 30, 2014 at 7:33 AM, Campbell, Paul (Paul) <[email protected]> wrote: > ** > > Here is a link to a BMC Communities article that is the best I’ve ever > seen about fast and list threads, good work from David Still > > > > > https://communities.bmc.com/community/bmcdn/bmc_atrium_and_foundation_technologies/bmc_remedy_ar_system/blog/2013/09/13/the-pulse-addressing-server-side-performance-problems--queues-threads > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Axton > *Sent:* Wednesday, April 30, 2014 1:20 AM > *To:* [email protected] > *Subject:* Re: Fast v.s. List Threads > > > > ** > > Just to help (maybe) solve a long standing problem, let me point this out. > > > > I ran a Google search for a quote from the excerpt you cited from the > product documentation: > > "The fast queue handles the operations that generally run to completion > quickly" > > > > Guess what result did not show up on the first page of results... BMC's > product documentation... What logic they have to withhold their > documentation from robots indexing it is beyond me. If memory serves me > correctly BMC has gone to lengths to ensure that APIs, documentation, > javadoc, systematic workflow documentation, etc. are not available on the > web. > > > > Maybe someone can help me understand the logic here because it eludes me... > > > > On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow < > [email protected]> wrote: > > ** > > This is straight out of the ARS configuration guide: > > > > *Fast queue* > > The fast queue handles the operations that generally run to completion > quickly > > without blocking access to the database. The fast queue handles all server > > operations, except for: > > Administrative operations that restructure the database. These > operations use > > the administration queue. > > The ARExport, ARGetListEntry, ARGetListEntryWithFields, and > > ARGetEntryStatistics, and other API calls (which use the list queue). > > For more information about API calls, see the *C API Reference*. > > One or more threads can serve the fast queue if a fast queue is > configured. To > > configure a fast queue, see “Defining queues and configuring threads” on > > page 160*.* > > > > *List queue* > > The list queue handles AR System operations that might require significant > time, > > block access to the database, or both. Examples of these operations include > > ARExport, ARGetListEntry, ARGetListEntryWithFields, and > > ARGetEntryStatistics. > > One or more threads can serve the list queue if a list queue is > configured. To > > configure a list queue, see “Defining queues and configuring threads” on > page 160. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Andrew Fremont > *Sent:* Tuesday, April 29, 2014 1:40 PM > *To:* [email protected] > *Subject:* Fast v.s. List Threads > > > > ** > > Hi, > > What are the main differences between the two? I can't any docs about > these threads. > > Which one handle the requests from users via Mid-tier, or WUT clients. > > Thanks > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 > Internal Virus Database is out of date. > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
