Home/ Questions/Q 7843495
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T16:33:50+00:00

This may not be suitable here, please feel free to move, shout or abuse

  • 0

This may not be suitable here, please feel free to move, shout or abuse if so.

We currently have a console application that get started by another and passed in an ID of the ‘job’, this job will have multiple records that need to be processed. A simple explanation of the flow would be;

Starts 50 threads

Gets records to be processed.
if records > 0 see what threads are not still busy and send it some information.
if records = 0 update something else and exit.
Get more records.
Loop.

Now, I am looking to convert this into a ‘polling’ service that is continually running and when new records are available, process them. To take what I have and convert this is fairly simple, but the threads stuff is old and probably outdated.

I was looking to refactor most if not all and use Task.Parallel to process the items. However, I am struggling to get a suitable framework for polling and then processing the items and was looking for suggestions on how to achieve this.

Pretty vague I know, but hopefully enough to give some kind of input.

Many thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From my experience and this msdn quote:

    More efficient and more scalable use of system resources.

    Behind the scenes, tasks are queued to the ThreadPool, which has been
    enhanced with algorithms (like hill-climbing) that determine and
    adjust to the number of threads that maximizes throughput. This makes
    tasks relatively lightweight, and you can create many of them to
    enable fine-grained parallelism. To complement this, widely-known
    work-stealing algorithms are employed to provide load-balancing.

    You simply shouldn’t care about how many tasks is a good number, or how to create a system where you load balance the threading involved.

    Simply use:

    Task.Factory.StartNew(() => DoSomeWork());

    Every time you want to run something asynchronously, it does all the smart job behind the curtain.

    Now since you’re likely to create tasks in a loop, please be extra-careful not to introduce a closure bug many people had (including me), which you can look up here.

    I have a windows service that runs from 1 to 500 Tasks, and never had trouble.

    Hope this helps,

    Bab.

    • 0