CODEWITHSUNDEEP
aspnetboilerplate
grinay
grinay

Reputation: 758

DbContext per request aspboilerplate

I need to implement multithreading background job for import file. I have implemented it with background job(Hangfire). But if i use one thread it goes very slow. The function look like this.

I using non-transaction unit to save changes to db immediately.

var contactFound = await _contactRepository.FirstOrDefaultAsync(x => x.Email.ToLower() == contact.Email.ToLower());

            if (contactFound != null)
            {
                await _bjInfoManager.AddLog(args.JobId, "Found duplicated email: " + contact.Email);

            }
            else
            {
                contact.ContactListId = args.ContactListId;
                contact.Email = contact.Email.ToLower();

                await _contactRepository.InsertAsync(contact);

                //Save changes in db
                await CurrentUnitOfWork.SaveChangesAsync();
            }

The problem occur when I tries to use this with Producer-Consumer Dataflow Pattern. I throws the exception "A second operation started on this context before a previous asynchronous operation completed."

The question is how to create isolated DbContext inside this method. Please help me.

Upvotes: 2

Views: 947

Answers (1)

Alper Ebicoglu
Alper Ebicoglu

Reputation: 9614

Transactions should not be multi-threaded. If you create a new task/thread in a UOW, you can create a seperated UOW using IUnitOfWork.Begin(TransactionScopeOption.RequiresNew) in a using block.

See the links

If you are using Microsoft SQL Server, then I recommend you to use bulk insert. It's super fast than entity framework.

https://learn.microsoft.com/en-us/sql/t-sql/statements/bulk-insert-transact-sql

Upvotes: 1

Related Questions