Problem with intensive locking (deadlocks?) during execution of system_1_test ?
Testing system_1 test under high load by executing many threads (above 20), I noticed that concurrency level is very low in spite of having intensive thread traffic in MSSQL servers.
System_1 test schema consists of two tables (tb1 & tb2), triggers, transactions and several stored PROCEDURES. When they are executed on different-different thread with different operations like insertion, deletion, updation, calling stored procedures, triggering transactions and other modifications in the table, why concurrency level is decreasing in MSSQL?
I think there must be some fault in thread locking mechanism which causes decrease in concurrency on such workloads.
“Well, let’s have some suggestions.”


