Load Testing Results Might Not Be What You Think

SQL Server Best Practices
SQL Server Best Practices
Bottlenecks in your testing tools, infrastructure, or methodology might just hurt your load test results, and the results can skew your metrics.

For example…

A few weeks ago we were running an iperf load test to see what improvements (if any) could be made to the configuration of a Windows Server networking stack. Setting up iperf for maximum throughput testing is easy.

iperf1

iperf2

The base test proved pretty fast, too!

iperf3

This testing was performed on our new 10GbE lab environment without jumbo frames enabled in the guest. We’ve got a Cisco Nexus 5k underneath this environment, so it is nice and fast.

We wanted to see the performance improvements with keeping this stream of data on the backplane of one physical server in our VM lab. We moved both of these VMs to the same host. Performing the same test should improve performance. I’ve seen upwards of a 16x performance improvement on a 1GbE network, so we should see at least a decent improvement on 10GbE, right?

The next test is after we moved them to the same host.

iperf4

It’s virtually (no pun intended) identical.

 

OK. So, let’s try to make Windows a bit more efficient.

autotunedisable

The results show a bit of improvement.

Continue reading on DavidKlee.net.

54321
(0 votes. Average 0 of 5)
Leave a reply

Your email address will not be published. Required fields are marked *