Skip to main content

Lambda expression and threads

If you are working with C# I’m pretty sure that you used a lambda expression (an action, a predicate, a delegate or a function). Basically you can define a block of code inline (function) and execute this code when you need it.
For all of you, that already used this features of C# I have a simple question:
     Does the lambda expression executes on the same thread or is executing on a different thread?
This information can be very important because running code on a different thread can be expensive. Not only this, there are times when we can have content that is static on the thread and not on our current process.
The simplest way to check this is to write a simple console application that displays the thread id.
class Program
{
    static void Main(string[] args)
    {
        DisplayCurrentThreadId();
        Action myAction = DisplayCurrentThreadId;
        myAction.Invoke();
        myAction.Invoke();
        DisplayCurrentThreadId();

        Console.ReadKey();
    }

    static void DisplayCurrentThreadId()
   {
        Console.WriteLine(Thread.CurrentThread.ManagedThreadId);
    }
}
The output of this was:

We saw that the lambda expression is executed on the same thread.
But what do you think about calling a lambda expression in an async manner? Does the code be executed on the same thread or on a different thread? To be able to test this we will modify our test code:
class Program
{
    static void Main(string[] args)
    {
        DisplayCurrentThreadId();
        Action myAction = DisplayCurrentThreadId;
        myAction.BeginInvoke(new AsyncCallback((r) => { }), null);
        myAction.BeginInvoke(new AsyncCallback((r) => { }), null);
        DisplayCurrentThreadId();
        Console.ReadKey();
    }
    static void DisplayCurrentThreadId()
    {
        Console.WriteLine(Thread.CurrentThread.ManagedThreadId);
    }
}
The output is:
By calling more than one time the lambda expression in an async method we can notice that there are cases when the async calls are executed on the same thread or on different thread. This thread are managed by .NET core and are reused when is possible.
In conclusion, executing a lambda expression in a sync way will execute the code on the same thread as the caller.

Comments

  1. It's somehow expected, since delegate.BeginInvoke will us the thread pool, which contains also the current thread.. It's similar to a call to ThreadPool.QueueUserWorkItem just a bit slower as far as I remember.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see