- Multithreading in C# 5.0 Cookbook
- Eugene Agafonov
- 364字
- 2021-07-21 18:10:01
Using the SemaphoreSlim construct
This recipe will show how to SemaphoreSlim
is a lightweight version of Semaphore
; it limits the number of threads that can access a resource concurrently.
Getting ready
To step through this recipe, you will need Visual Studio 2012. There are no other prerequisites. The source code for this recipe could be found at BookSamples\Chapter2\Recipe3
.
How to do it...
To understand limiting a multithreaded access to a resource with the help of the SemaphoreSlim
construct, perform the following steps:
- Start Visual Studio 2012. Create a new C# Console Application project.
- In the
Program.cs
file add the followingusing
directives:using System; using System.Threading;
- Below the
Main
method, add the following code snippet:static SemaphoreSlim _semaphore = new SemaphoreSlim(4);
static void AccessDatabase(string name, int seconds) { Console.WriteLine("{0} waits to access a database", name); _semaphore.Wait(); Console.WriteLine("{0} was granted an access to a database",name); Thread.Sleep(TimeSpan.FromSeconds(seconds)); Console.WriteLine("{0} is completed", name); _semaphore.Release(); }
- Inside the
Main
method, add the following code snippet:for (int i = 1; i <= 6; i++) { string threadName = "Thread " + i; int secondsToWait = 2 + 2*i; var t = new Thread(() => AccessDatabase(threadName, secondsToWait)); t.Start(); }
- Run the program.
How it works...
When the main program starts, it creates a SemaphoreSlim
instance, specifying the number of concurrent threads allowed in its constructor. Then it starts six threads with different names and start times to run.
Every thread is trying to acquire an access to a database, but we restrict the number of concurrent accesses to a database by four threads with the help of a semaphore. When four threads get an access to a database, the other two threads wait until one of the previous threads finishes its work and signals by calling the _semaphore.Release
method.
There's more…
Here we use a hybrid construct, which allows us to save a context switch in cases where the wait time is less. However, there is an older version of this construct called Semaphore
. This version is a pure, kernel-time construct. There is no sense in using it, except in one very important scenario; we can create a named semaphore like a named mutex and use it to synchronize threads in different programs. SemaphoreSlim
does not use Windows kernel semaphores and does not support interprocess synchronization, so use Semaphore
in this case.
- 演進式架構(原書第2版)
- FuelPHP Application Development Blueprints
- Microsoft Application Virtualization Cookbook
- The Computer Vision Workshop
- Building Serverless Applications with Python
- Learning SciPy for Numerical and Scientific Computing(Second Edition)
- Working with Odoo
- PHP 7從零基礎到項目實戰
- 汽車人機交互界面整合設計
- SQL Server 2016 從入門到實戰(視頻教學版)
- Illustrator CS6設計與應用任務教程
- C++程序設計教程
- Python一行流:像專家一樣寫代碼
- 深入淺出 HTTPS:從原理到實戰
- Joomla!Search Engine Optimization