It seems that, when multiple instances of DbContext exist on multiple threads and each thread calls SaveChanges(), there is some form of resource contention in EF itself limiting throughput.
VS2012's profiler says there is 61% contention for a resource called Handle 2 in a specific run of a specific use case.
Details are outlined on Stack Overflow:
http://stackoverflow.com/q/13182603/141172
VS2012's profiler says there is 61% contention for a resource called Handle 2 in a specific run of a specific use case.
Details are outlined on Stack Overflow:
http://stackoverflow.com/q/13182603/141172