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<http://www.avg.com> Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
