Skip to main content

Taks and Thread.Sleep

What is the problem of the following code?
Task.Factory.StartNew(() =>
    {
        while (true)
        {
            Console.WriteLine("@ " + DateTime.Now.ToString());
            Thread.Sleep(TimeSpan.FromSeconds(2));
        }
    });
var task = Task.Factory.StartNew(() =>
{
    while (true)
    {
        Console.WriteLine("!  " + DateTime.Now.ToString());
        Thread.Sleep(TimeSpan.FromSeconds(4));
    }
});

Task.WaitAll(task);
The main problem is related to Thread.Sleep. Using this method in combination with tasks we can gen odd behavior and in the end the performance of the tasks can be affected. One of the behavior that we could get is related to how the sleep period – that will not be the same as we expect ("random" sleep interval).
This occurs because of the TPL behavior, which will not guarantee that each task will have a dedicated thread where he can run.
What we should do to resolve this problem?
We have two possible solution.
1. One solution is to create a timer for each task. This would work 100% and for this example the solution is the way how we should implemented this from the start.
2. In other cases we wouldn't be able to use timers and we would like to be able to put the task in sleep. In the case we have a long running task, than we could set the TaskCreationOption to LongRunning. This will notify TPL that this task is a long running task and will create a dedicate thread for it.
Task.Factory.StartNew(() =>
    {
        while (true)
        {
            Console.WriteLine("@ " + DateTime.Now.ToString());
            Thread.Sleep(TimeSpan.FromSeconds(2));
        }
    },TaskCreationOptions.LongRunning);
var task = Task.Factory.StartNew(() =>
{
    while (true)
    {
        Console.WriteLine("!  " + DateTime.Now.ToString());
        Thread.Sleep(TimeSpan.FromSeconds(4));
    }
}, TaskCreationOptions.LongRunning);

Task.WaitAll(task);

Comments

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

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

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...