Tukukkk

I have .NET Core Web API solution. In each call, I need to perform some database operations.
The issue is at a time multiple db connections get opened & close. So to avoid it, I want to implement Queue of objects to be sent to database and then want a separate thread to perform db operation.

I've tried some code as below. But here, Consumer thread never executes assigned function. There is no separate thread for Producer, I am simply feeding queue with object.

What modifications I should do? Need some guidance as I'm new to Threading stuff.

  public static class BlockingQueue

{

    public static Queue<WebServiceLogModel> queue;

    static BlockingQueue()

    {

        queue = new Queue<WebServiceLogModel>();



    }



    public static object Dequeue()

    {

        lock (queue)

        {

            while (queue.Count == 0)

            {

                Monitor.Wait(queue);

            }

            return queue.Dequeue();

        }

    }

    public static void Enqueue(WebServiceLogModel webServiceLog)

    {

        lock (queue)

        {

            queue.Enqueue(webServiceLog);

            Monitor.Pulse(queue);

        }

    }



    public static void ConsumerThread(IConfiguration configuration)

    {

        WebServiceLogModel webServiceLog = (WebServiceLogModel)Dequeue();

        webServiceLog.SaveWebServiceLog(configuration);

    }



   public static void ProducerThread(WebServiceLogModel webServiceLog)

    {

        Enqueue(webServiceLog);

         Thread.Sleep(100);

    }

}

I've created and started thread in StartUp.cs:

    public Startup(IConfiguration configuration)

    {

        Thread t = new Thread(() => BlockingQueue.ConsumerThread(configuration));

        t.Start();

    }

In Controller, I've written code to feed the queue:

    [HttpGet]

    [Route("abc")]

    public IActionResult GetData()

    {

        BlockingQueue.ProducerThread(logModel);

        return StatusCode(HttpContext.Response.StatusCode = (int)HttpStatusCode.NotFound, ApplicationConstants.Message.NoBatchHistoryInfo);

    }

First of all, try to avoid static classes and methods. Use pattern singleton in that case (and if you really need this).
Second, try to avoid lock, Monitor - those concurrency primitives significantly lower your performance.
In such situation, you can use BlockingCollection<> as 'Adam G' mentioned above, or you can develop your own solution.

public class Service : IDisposable

{

    private readonly BlockingCollection<WebServiceLogModel> _packets =

        new BlockingCollection<WebServiceLogModel>();

    private Task _task;

    private volatile bool _active;

    private static readonly TimeSpan WaitTimeout = TimeSpan.FromSeconds(1);



    public Service()

    {

        _active = true;

        _task = ExecTaskInternal();

    }



    public void Enqueue(WebServiceLogModel model)

    {

        _packets.Add(model);

    }



    public void Dispose()

    {

        _active = false;

    }



    private async Task ExecTaskInternal()

    {

        while (_active)

        {

            if (_packets.TryTake(out WebServiceLogModel model))

            {

                // TODO: whatever you need

            }

            else

            {

                await Task.Delay(WaitTimeout);

            }

        }

    }

}



public class MyController : Controller

{

    [HttpGet]

    [Route("abc")]

    public IActionResult GetData([FromServices] Service service)

    {

        // receive model form somewhere

        WebServiceLogModel model = FetchModel();

        // enqueue model

        service.Enqueue(model);

        // TODO: return what you need

    }

}

And in Startup:

public class Startup

{

    public void ConfigureServices(IServiceCollection services)

    {

        services.AddSingleton<Service>();

        // TODO: other init staffs

    }

}

You even can add Start/Stop methods to the service instead of implementing IDisposable and start your service in the startup class in the method Configure(IApplicationBuilder app).

I think your consumer thread is executed just once if there is something in the queue and then immediately returns. If you want to have a thread doing work in background, which is started just once, it should never return and should catch all exceptions. Your thread from BlockingQueue.ConsumerThread is invoked once in Stratup and returns.

Also please be aware that doing such solution is not safe. ASP.NET doesn't guarantee background threads to be running if there are no requests coming in. Your application pool can recycle (and by default it recycles after 20 minutes of inactivity or every 27 hours), so there is a chance that your background code won't be executed for some queue items.

Also, while it doesn't solve all issues, I would suggest using https://www.hangfire.io/ to do background tasks in ASP.NET server. It has persistence layer, can retry jobs and has simple API's. In your request handler you can push new jobs to Hangfire and then have just 1 job processor thread.