We are planning to migrate from a physical machine to Hyper-V structure.
In our Hyper-V environment test, we get, in simple queries, better (or almost the same) response time than in physical machine.
But, in more sophisticate forms, the performance decreases about 10 times. For example: in physical machine the response time is less than 2" versus 22" in VM.
Could you help me, please?
Here are the details:
1. Isolated VBA code:
WkConnectionString= "Provider=SQLOLEDB;Data Source=INSTANCENAME;Initial Catalog=DBNAME;User ID=USERID;Password=XXXXX;"
For WkI = 1 To 20
Set CnConexioDBNAME = New ADODB.Connection
CnConexioDBNAME.Open WkConnectionString
CnConexioDBNAME.Close
Set CnConexioDBNAME = Nothing
Next WkI
** This code takes less than 2" to answer when runs in physical machine and 22" in VM
2. MsAccess forms:
- The more sophisticated ones, have 12 Combo Box with a pass-trough query as data source in every one.
- Plus, three sub forms.
3. Languages and OS:
- Forms developed in MsAccess 2013 (x86) with VBA.
- SQL Server 2014 (SP3) (x64)
- Installed in Windows Server 2012 R2 Standard (in the Physical machine)
- DELL. 16Gb RAM. 2.4Ghz (2 processors). x64.
- Installed in Windows Server 2016 Standard (in the Hyper-V VM)
- DELL. 8Gb RAM, 1.7Gh, SSD. x64
- Microsoft ODBC Driver 13 for SQL Server (x86)
3. Hyper-V VM (hyperv-2016 core)
- VHDX on SSD
- Virtual machine Switch external
- Generation 2.
- Configuration 8.0
4. Clients
- When accessing from W7 or WServer 2008 to the VM, the response time is 8"
- When accessing form W10 or WServer 2012 to the VM, the response time is 22"
- However, in both cases, when accessing to the physical machine, the response time is less than 2"
5. Hardware
- NIC Intel i350,i210, broadcom netxtreme
- VMQ: Disabled
- BIOS: saving energy : High Performance power plan