Skip to content

SQL Server 2019 #143

Answered by sm-shaw
vsudenko asked this question in Q&A
Discussion options

You must be logged in to vote

The first reaction is that these numbers are relatively quite low - a simple test with SQL 2019 on an far from state of the art dev PC gives me 150134 NOPM from 345996 TPM. So the first step would be use SSMS Activity Monitor and identify the highest resource wait. IO for logging is often a bottleneck but clearly there is a dependency on the CPU resource as well.
Also is this using the same version of HammerDB for both tests?- ie you are currently testing both database versions at the same time with the same stack? - if not what are the versions and are they both running on Windows with the same ODBC client library?

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by abondvt89
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #143 on December 16, 2020 18:02.