Creating a execution queue by using Task.ContinueWith?

Question

I have several actions that I want to execute in the background, but they have to be executed synchronously one after the other.

I was wondering if it's a good idea to use the Task.ContinueWith method to achieve this. Do you foresee any problems with this?

My code looks something like this:

private object syncRoot =new object();
private Task latestTask;

public void EnqueueAction(System.Action action)
{
    lock (syncRoot)
    {
        if (latestTask == null)
            latestTask = Task.Factory.StartNew(action);
        else
            latestTask = latestTask.ContinueWith(tsk => action());
    }
}

score 9 · Answer 1 · edited Jul 14 '12 at 01:07

There is one flaw with this, which I recently discovered myself because I am also using this method of ensuring tasks execute sequentially.

In my application I had thousands of instances of these mini-queues and quickly discovered I was having memory issues. Since these queues were often idle I was holding onto the last completed task object for a long time and preventing garbage collection. Since the result object of the last completed task was often over 85,000 bytes it was allocated to Large Object Heap (which does not perform compaction during garbage collection). This resulted in fragmentation of the LOH and the process continuously growing in size.

As a hack to avoid this, you can schedule a no-op task right after the real one within your lock. For a real solution, I will need to move to a different method of controlling the scheduling.

score 5 · Accepted Answer · answered Jul 21 '11 at 17:31

5

This should work as designed (using the fact that TPL will schedule the continuation immediately if the corresponding task already has completed).

Personally in this case I would just use a dedicated thread using a concurrent queue (ConcurrentQueue) to draw tasks from - this is more explicit but easier to parse reading the code, especially if you want to find out i.e. how many tasks are currently queued etc.

answered Jul 21 '11 at 17:31

BrokenGlass

158,293
28
286
335

1

An improvement would be to use a BlockingCollection around the ConcurrentQueue. Then one can dispatch a Task / Worker thread that just uses a foreach over the blocking collection. The foreach will "hang" until a new item is added to the queue or CompleteAdding() is called on the blocking collection. – Martin Ullrich Jun 22 '15 at 08:17

score 0 · Answer 3 · answered May 09 '14 at 15:21

0

I used this snippet and have seem to get it work as designed. The number of instances in my case does not runs in to thousands, but in single digit. Nevertheless, no issues so far.

I would be interested in the ConcurrentQueue example, if there is any?

Thanks

answered May 09 '14 at 15:21

zyzzyxx

323
2
9

For a super simple queue this works well for me still. But form more involved task queues I've started to use [Dataflow](http://msdn.microsoft.com/en-us/library/hh228603(v=vs.110).aspx) more. – lukebuehler May 09 '14 at 18:34

Creating a execution queue by using Task.ContinueWith?

3 Answers3

Linked