@DustinB3403 said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2016 on same host:
What kind of IOPS are you getting from the hypervisor?
How is the server configured?
How many concurrent users, 10?
Have you monitored the performance to try and determine where the slow down is occurring?
No idea on the IOPs. I'll install "Zabbix" mentioned in your other post and report back.
Dell R540 Server with the following specs:
Two Xeon Gold 5117 2.27GHz 14 Core CPUs
(2 sockets, 28 cores, 56 logical processors)
128GB Ram
Two 500GB SSD drives in RAID1 for the OS
Four 1TB SSD drives in RAID10 for SQL Data and VMs
Windows Server 2016 Standard
MS SQL Server 2014 Standard
Server Runs AD, DHCP Server, DNS Server, SQL, and the VMs.
VMS:
Nine Windows 10 Enterprise VMs
PCs:
Six Windows 10 Pro Workstations also accessing the SQL Data
@scottalanmiller said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2016 on same host:
Check the network setup, make sure that the database server and the Windows 10 client VMs all have proper network drivers configured. Could be a point of issues if not.
I'll check this.
@scottalanmiller said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2016 on same host:
@JasGot said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2016 on same host:
I've had chats with the developers, and they suggest the SQL server and application are all optimized. Leaving me with SQL Query issues in and out of the VMs.
No way to know BUT the real issue is that it is slower than the same system before. That's the key here.
Can you describe the former setup?
I minced my words and created confusion. It's all new hardware and design. Previously it was SBS2011 with SQL installed and another server running Windows Server 2008 with Terminal Services. Both with spinning 10K drives and 32GB ram. It wasn't fast, but it was faster than this.
@Dashrender said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2016 on same host:
How much RAM do the VMs have assigned?
The Dom0 Windows instance can use all the RAM not assigned to a VM ( I think ), so that's likely one place it could be winning, depending upon how the RAM is divied up.
I had them set for 6GB Dynamic Ram They never use more than 2GB at peak, usually around 1.7 or 1.8. I changed a couple of them to 6GB NOT Dynamic and did not see any change in the user experience.
I also had them set for two vCPUs with 10% for VM Reserve, VM Limit, and Relative weight.
I tried 3 vCPUs, no change, and then I went to one vCPU with 100% VM Reserve, VM Limit, and Relative weight. I thought I noticed an improvement, but I can't be sure via the user interface, hopefully Zabbix will shed some light.....
@Dashrender said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2016 on same host:
How much RAM do the VMs have assigned?
The Dom0 Windows instance can use all the RAM not assigned to a VM ( I think ), so that's likely one place it could be winning, depending upon how the RAM is divied up.
I'll list what I know about the memory usage, not sure how it is spread about:
Total Physical RAM: 128GB
In use Compressed: 58GB
Available: 70GB
Committed: 60GB/147GB
Cached: 35.5GB
Paged pool: 592MB
Non Paged Pool: 1.92GB
Hardware Reserved 318MB
Speed 2666MHz
I haven't seem RAM usage above 50% and I have not seen CPU usage (taskmanager) above 7%
I'm going to go and grab Zabbix now.