Threading Simplified: Part 8 (Synchronization Basics and Thread Blocking)

I am again here to continue the discussion around Threading. Today we will discuss about Thread Synchronization Fundamentals and related concepts.

In case you didn’t have a look at the previous posts, you can go through them below.

Let’s start by posing questions to understand the concepts.

Why Synchronization

When working in multithreaded environments, it’s hard to predict which thread is active and executing any piece of code. This becomes even harder when all the threads are executing shared or common code. So to answer, synchronization is required to predict the outcome in multithreaded environment.

What are the ways to handle synchronization?

There are several ways and methods to handle synchronization as in the following:

Blocking
o Sleep
o Join
o Task.Wait
Locking
o Exclusive (Lock or Monitor, Mutex (Local/ System), Spin Lock)
o Non-exclusive (Semaphore (Local/ System), Semaphore Slim, Reader/Writer Lock)
Signaling
o Event wait handles (AutoResetEvent/ ManualResetEvent)
o Wait/ Pulse
o Countdown event
o Barrier class
Non-blocking
o Memory Barrier
o Volatile Read/ Write classes
o Volatile keyword
o Interlocked class

As you can see thread synchronization has lot of contents and hence we will take them one by one. In this article, we will focus on thread blocking, as it’s easier to understand.

Thread Blocking

The philosophy behind thread blocking is to let another thread wait until current thread is either finished or has consumed a certain amount of time.

The good part of thread blocking is that the waiting thread doesn’t consume any CPU slice until its reactivated back or unblocked.

Thread reactivation or unblocking can also happen using Thread.Interrupt or Thread.Abort methods.

Just to add, context switching happens when thread blocks or unblocks that adds an overhead of few microseconds.

Let’s talk about one of the important enum called ThreadState that helps in determining if the current thread is blocked or not.

ThreadState(System.Threading) enum has several values but notably are the following.

Running
Background
Stopped
Suspended
Aborted
WaitSleepJoin

Please note that there is one more ThreadState enum in System.Diagnostics namespace so don’t get confused with that. As per MSDN documentation, these should only be used in debugging scenarios as at times these enums don’t yield correct thread state.

Now let’s see something in action.

Let’s go through the code to understand how constructs of thread blocking really works.

static Thread thread1 = null;
static Thread thread2 = null;
static void DoWork1()
{
Console.WriteLine("Inside DoWork1, Thread 1 state: {0}", thread1.ThreadState);
Console.WriteLine("Inside DoWork1, Thread 2 state: {0}", thread2.ThreadState);
for (int i = 0; i < 3; i++)
{
Console.WriteLine("DoWork1: " + i);
}
}
static void DoWork2()
{
Console.WriteLine("Inside DoWork2, Thread 1 state: {0}", thread1.ThreadState);
Console.WriteLine("Inside DoWork2, Thread 2 state: {0}", thread2.ThreadState);
for (int i = 0; i < 3; i++)
{
Console.WriteLine("DoWork2: " + i);
}
}
static int DoWork3()
{
////In real word, some expensive operation will be there.
////Putting sleep to simulate load.
Thread.Sleep(1000);
return 5;
}
static void TestJoin()
{
Console.WriteLine("\nTesting Join");
thread1 = new Thread(DoWork1);
thread2 = new Thread(DoWork2);
thread1.Start();
thread1.Join();
thread2.Start();
}
static void TestSleep()
{
Console.WriteLine("\nTesting Sleep");
Console.WriteLine("Thread sleep started time: {0}", DateTime.Now);
Thread.Sleep(2000);
Console.WriteLine("Thread sleep ended time: {0}", DateTime.Now);
}
static void TestTaskWait()
{
Console.WriteLine("\nTesting Task.Wait");
Console.WriteLine("Task started time: {0}", DateTime.Now);
var task = Task.Factory.StartNew(DoWork3);
task.Wait();
Console.WriteLine("Task ended time: {0}, Result: {1}", DateTime.Now, task.Result);
}
static void Main(string[] args)
{
Console.Title = "Thread Synchronization Demo";
TestSleep();
TestJoin();
TestTaskWait();
}

In the code, you can see that we have three methods TestSleep, TestJoin and TestTaskWait to understand thread blocking. The following is the output of the code.

Output

You can see in the output that,

We have put 2000 ms of sleep time and hence there is 2 seconds of difference in sleep starting time and ending time.
Since we have put Join in thread1, thread2 (DoWork2) is executing only once thread1 is finished.
The thread state of thread1 is changed from “Running” to “Stopped” when thread2 started “Running”.
Task.Wait holds the thread execution until it’s finished (unlike async/await which we will discuss later)

Hope you have liked the article. I look forward for your comments/suggestions.

17 Comments

Join the conversation! Your thoughts help the community grow.

Prakash Tripathi10y ago
Thnx Jothimangala.
Jothimangala Ramanathan10y ago
easy to understand; nicely summarized with examples
Prakash Tripathi10y ago
Thnx Kumaresh.
Prakash Tripathi10y ago
Thnx Karthiga.
Kumaresh Rajalingam10y ago
good one
Kumaresh Rajalingam10y ago
Nice explanation
Sr Karthiga10y ago
good one
Sr Karthiga10y ago
Nice explanation
Prakash Tripathi10y ago
Thnx Shubham.
Shubham Kumar10y ago
Very descriptive
Prakash Tripathi10y ago
Thnx Ankit.
Ankit Bansal10y ago
Nice share..thanks..
Prakash Tripathi10y ago
Thnx Debasis.
Debasis Saha10y ago
Good One..
Prakash Tripathi10y ago
Thnx Ibrahim.
Mohammed Ibrahim10y ago
nice
Santhakumar Munuswamy10y ago
Thanks for nice article.