Click here to Skip to main content
12,950,099 members (54,668 online)
Click here to Skip to main content
Add your own
alternative version


111 bookmarked
Posted 1 Feb 2003

Work Queue

, 1 Feb 2003
Rate this:
Please Sign up or sign in to vote.
Simple and elegant thread pool.
<!-- Article image -->

Sample Image - Work_Queue.gif

<!-- Add the rest of your HTML here -->


In real time systems that need to respond to and process different tasks in the fastest possible way, and the tasks can be processed concurrently, there needs to be a number of thread waiting, willing, and able to perform the tasks at hand. This can be achieved with a specific structural scheme for each specific job, or with a generic method called thread pool. The work queue is a simple and elegant type of thread pool that creates requested number of threads at its creation and manages a queue of different work items that implement the specific tasks, where each work item in his turn gets a thread that works and processes it.

How to Use

First a new type of work item needs to be defined in a format that can be processed by the work queue.   To do this, you need to implement a work item class that inherits from the base work item class WorkItemBase. The WorkItemBase has two abstract functions that need to be implemented.  The first, DoWork, is the method that will be executed by the free thread when the work item gets its turn in the queue.  The second, Abort, is called when the queue is destroyed prior to the work item getting its turn. The specific work item should be implemented as follows.

class SpecificWorkItem : public WorkItemBase
    void   DoWork(void* pThreadContext);
    void   Abort();

 //memeber variables needed here

void   SpecificWorkItem::DoWork(void* pThreadContext)
  //Notify Start
  //proccessing done here
  //Notify Finish
  //free all that was occupied

void   SpecificWorkItem::Abort()
  //Notify aborted
  //free all that was occupied

Note that a different types of work items can be processed in the same work queue.  In the work queue, first the Create function needs to be called where the first parameter is the number of threads and the second is an array of pointers to a thread data structure.  This structures can be used as a working surface for each of the threads. This is used to reduce the local variables declared in the

function and the dynamic allocation for each item that is being processed, for optimization of processing.

CWorkQueue WorkQueue;

As you can see in the code, one can ignore the second parameter which has the default value is NULL. Next, to insert a work item into the queue you need to call InsertWorkItem with the newly created work item. This function can be called asynchronously.

SpecificWorkItem* pWorkItem = new SpecificWorkItem()
// prepare the work item for the task

After using the work queue you must call the Destroy function. This function will wait until all threads have finished processing the work items that are already out of the queue, then calls the Abort function of each of the work items that are waiting in the queue to be processed.



The work queue is implemented using an STL queue of work items which is guaranteed to work in an asynchronous system by a mutual exclusion lock, a semaphore that is initialized with an initial count of zero, an abort event, and an array of threads that are created to run a particular function.  This function is waiting on the two asynchronous objects.   First the abort event that, if set, the thread will return from the function.  Second, semaphore, that if released, the thread will extract the next item in the queue and call its DoWork function. At the insert function the semaphore is released (by 1) after inserting the work item, allowing one of the threads to do attach to the worker function. When the Destroy function is called in turn, the abort event is set and the function waits for all threads to terminate.  For each of the work item that are left in the queue, it calls their Abort function.

Demo project

The demo project is a project I included merely to illustrate the way the work queue performs. What you need to do to work it is:

  1. determine the number of thread you want
  2. click the create button to create the work queue
  3. insert work item to the queue as you please by clicking the insert item button
  4. destroy the work queue click the destroy button.


thanks to Hans Dietrich for the XlistCtrl


This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here


About the Author

Uri Twig
Web Developer
Israel Israel
4 years expirience coding C++ with MFC & STL and coding C for Windows XP/2K internals (Drivers).

I Love what I do.

For pastime activities:
Fun & Games

You may also be interested in...


Comments and Discussions

AnswerRe: Handle leaks Pin
Yves Tkaczyk20-Oct-05 10:47
memberYves Tkaczyk20-Oct-05 10:47 
QuestionPass CMainFrame pointer? Pin
ehh17-Feb-05 5:06
memberehh17-Feb-05 5:06 
AnswerRe: Pass CMainFrame pointer? Pin
Dan Madden8-Jun-05 11:15
memberDan Madden8-Jun-05 11:15 
AnswerRe: Pass CMainFrame pointer? Pin
Blake Miller25-Aug-05 8:11
memberBlake Miller25-Aug-05 8:11 
GeneralRe: Pass CMainFrame pointer? Pin
ehh1-Sep-05 3:36
memberehh1-Sep-05 3:36 
GeneralRe: Pass CMainFrame pointer? Pin
Blake Miller1-Sep-05 3:56
memberBlake Miller1-Sep-05 3:56 
GeneralTimeout Pin
dspeziale12-Dec-04 22:57
memberdspeziale12-Dec-04 22:57 
Generali wnt yours helpe Pin
sultan_saud1-Nov-04 2:55
membersultan_saud1-Nov-04 2:55 
GeneralUse CWinThread instead of ::CreateThread Pin
Andrey Del Pozo6-Sep-04 10:22
memberAndrey Del Pozo6-Sep-04 10:22 
GeneralRe: Use CWinThread instead of ::CreateThread Pin
Blake Miller25-Aug-05 8:05
memberBlake Miller25-Aug-05 8:05 
GeneralIO Completion port / QueueUserWorkItem Pin
Vladislav Gelfer6-Jun-04 10:42
memberVladislav Gelfer6-Jun-04 10:42 
GeneralMemory Problem with AdoConnection Pin
VietDelphi7-May-04 5:08
memberVietDelphi7-May-04 5:08 
GeneralRe: Memory Problem with AdoConnection Pin
Blake Miller25-Aug-05 8:00
memberBlake Miller25-Aug-05 8:00 
Generalmemory leaks Pin
Justin884811-Nov-03 20:44
memberJustin884811-Nov-03 20:44 
GeneralDetected Memory Leaks Pin
Kurt Muellner26-Aug-03 8:32
memberKurt Muellner26-Aug-03 8:32 
GeneralRe: Detected Memory Leaks Pin
Kurt Muellner26-Aug-03 20:25
memberKurt Muellner26-Aug-03 20:25 
QuestionDo IIS At a Core level works same way? Pin
vmalvania23-Jun-03 1:36
membervmalvania23-Jun-03 1:36 
QuestionHow do you know when the WorkQueue has finished? Pin
DJ MACROSS22-May-03 9:33
memberDJ MACROSS22-May-03 9:33 
AnswerRe: How do you know when the WorkQueue has finished? Pin
michael_cowan6-Nov-03 10:49
membermichael_cowan6-Nov-03 10:49 
GeneralRe: How do you know when the WorkQueue has finished? Pin
Daniel Madden6-Nov-03 21:55
memberDaniel Madden6-Nov-03 21:55 
GeneralRe: How do you know when the WorkQueue has finished? Pin
mcpata20027-May-04 18:44
membermcpata20027-May-04 18:44 
GeneralSimple Question Pin
Brad Loyd17-Apr-03 10:26
memberBrad Loyd17-Apr-03 10:26 
GeneralRe: Simple Question Pin
ming100025-Apr-03 8:49
memberming100025-Apr-03 8:49 
GeneralRe: Simple Question Pin
cvmanjesh11-Oct-07 21:08
membercvmanjesh11-Oct-07 21:08 
GeneralThreads keep alive...why? :( Pin
Martin_Viet10-Apr-03 7:20
memberMartin_Viet10-Apr-03 7:20 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.170525.1 | Last Updated 2 Feb 2003
Article Copyright 2003 by Uri Twig
Everything else Copyright © CodeProject, 1999-2017
Layout: fixed | fluid