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

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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...