Question

I’ve got a list of Foo IDs. I need to call a stored procedure for each ID.

e.g.

Guid[] siteIds = ...; // typically contains 100 to 300 elements
foreach (var id in siteIds)
{
   db.MySproc(id); // Executes some stored procedure.
}

Each call is pretty independent of the other rows, this shouldn’t be contentious in the database.

My question: would it be beneficial to parallelize this using Parallel.ForEach? Or is database IO going to be a bottleneck, and more threads would just result in more contention?

I would measure it myself, however, it’s difficult to measure this on my test environment where the data and load is much smaller than our real web server.

Answer 1

Out of curiosity, why do you want to optmize it with Parallel.ForEach and spawn threads / open connections / pass data / get response for every item instead of writing a simple “sproc” that will work with list of IDs instead of single ID?

From the first look, it should get you a lot more noticable improvement.