CODEWITHSUNDEEP
c#multithreading
Rudra
Rudra

Reputation: 383

Monitoring a multi-threaded application

I am writing a multi-thread application (using C#) where the job of each thread is to insert some data into database. As soon the thread completes its job of inserting data into database it becomes free (i.e. ready to insert another data into database). All the threads are reading data from a queue.

The problem is, how to monitor which thread has completed its current job and ready to take second job? Whether we can use C# task instead of thread and how?

Please note every thread is inserting data to the same database.

Upvotes: 0

Views: 68

Answers (2)

user5939410
user5939410

Reputation: 47

In my opinion you should use only Task not "Task in Thread". Tasks are more flexible and already implemented robustly. In your case you can create an Task[] (with 10 Tasks if you want) and to know if the task has completed his work you can check the Task.Result value if you have declared Task<\TResult> objects.

in this way you can have direct control of the processes during the asynchronous execution including exception handling.

Upvotes: 0

TomTom
TomTom

Reputation: 62137

The problem is, how to monitor which thread has completed its current job and ready to take second job?

Why would you do that? Threads created are looping until there is no data. If there is no thread (or less than wanted) and data arrives, start a new thread/task. Actually uses tasks. There is no need to monitor them. This would be ridiculously inefficient.

Whether we can use C# task instead of thread and how?

Yes, and it is as simple as "look up how to start a task, which google has an answer for". That said, your architecture likely needs adjustment - doing too many things in parallel will only waste memory, rather limit the number of active threads/tasks to a specific number.

Upvotes: 0

Related Questions