Network setup - Hyper-V
-
@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@reid-cooper said in Network setup - Hyper-V:
So the app is fast when using local storage and slow when using network storage? Seems like a not unexpected behaviour.
Except that it is. Of course running it locally with be always faster, but I'm talking about very significant slowdowns. I said above that I have done several of these servers for clients that use the software and have not had this issue.
Right, but difference now is - Windows server version and Hyper-V version? what about hardware differences?
Server 2016 is new. They all have been 2012 R2 and earlier. However the vendor says they have tested 2016 and had no problems. I don't know how much testing they have done with hyper-v (although they so support it).
Hardware is essentially the same setup.
-
When possible, you should have a copy of the data so you can just restore it to a test location for something like the following.
Windows 10 PC (Desktop/laptop hardware) put the data there and access it using the same client machine via the same switch as the server uses, see if there is a difference.
Then test the same setup with Server 2016 on that hardware.
-
I believe you said that you put the data directly on the Hyper-V host and shared it? if so, what was the outcome?
I also recall that you shared it from the VM, and accessed it on the Hyper-V host via that share, and it was slow - is that still the case?
-
Output from Physical Server:
ConnectionCountPerRssNetworkInterface : 4
DirectoryCacheEntriesMax : 16
DirectoryCacheEntrySizeMax : 65536
DirectoryCacheLifetime : 10
DormantFileLimit : 1023
EnableBandwidthThrottling : True
EnableByteRangeLockingOnReadOnlyFiles : True
EnableInsecureGuestLogons : True
EnableLargeMtu : True
EnableLoadBalanceScaleOut : True
EnableMultiChannel : True
EnableSecuritySignature : True
ExtendedSessionTimeout : 1000
FileInfoCacheEntriesMax : 64
FileInfoCacheLifetime : 10
FileNotFoundCacheEntriesMax : 128
FileNotFoundCacheLifetime : 5
KeepConn : 600
MaxCmds : 50
MaximumConnectionCountPerServer : 32
OplocksDisabled : False
RequireSecuritySignature : False
SessionTimeout : 60
UseOpportunisticLocking : True
WindowSizeThreshold : 1Output from Applications server:
ConnectionCountPerRssNetworkInterface : 4
DirectoryCacheEntriesMax : 16
DirectoryCacheEntrySizeMax : 65536
DirectoryCacheLifetime : 10
DormantFileLimit : 1023
EnableBandwidthThrottling : True
EnableByteRangeLockingOnReadOnlyFiles : True
EnableInsecureGuestLogons : True
EnableLargeMtu : True
EnableLoadBalanceScaleOut : True
EnableMultiChannel : True
EnableSecuritySignature : True
ExtendedSessionTimeout : 1000
FileInfoCacheEntriesMax : 64
FileInfoCacheLifetime : 10
FileNotFoundCacheEntriesMax : 128
FileNotFoundCacheLifetime : 5
KeepConn : 600
MaxCmds : 50
MaximumConnectionCountPerServer : 32
OplocksDisabled : False
RequireSecuritySignature : False
SessionTimeout : 60
UseOpportunisticLocking : True
WindowSizeThreshold : 1ServerName ShareName UserName Credential Dialect NumOpens
HOMETOWN-APPS Data HTVET\hvh2 HTVET\HVH2 3.1.1 1
HOMETOWN-APPS Data HTVET\HVH3 HTVET\HVH3 3.1.1 1
HOMETOWN-APPS Data HTVET\HVH8 HTVET\HVH8 3.1.1 1Output from one of the workstations:
ConnectionCountPerRssNetworkInterface : 4
DirectoryCacheEntriesMax : 16
DirectoryCacheEntrySizeMax : 65536
DirectoryCacheLifetime : 10
DormantFileLimit : 1023
EnableBandwidthThrottling : True
EnableByteRangeLockingOnReadOnlyFiles : True
EnableInsecureGuestLogons : True
EnableLargeMtu : True
EnableLoadBalanceScaleOut : True
EnableMultiChannel : True
EnableSecuritySignature : True
ExtendedSessionTimeout : 1000
FileInfoCacheEntriesMax : 64
FileInfoCacheLifetime : 10
FileNotFoundCacheEntriesMax : 128
FileNotFoundCacheLifetime : 5
KeepConn : 600
MaxCmds : 50
MaximumConnectionCountPerServer : 32
OplocksDisabled : False
RequireSecuritySignature : False
SessionTimeout : 60
UseOpportunisticLocking : True
WindowSizeThreshold : 8ServerName ShareName UserName Credential Dialect NumOpens
HOMETOWN-APPS Data HTVET\hvh HTVET.LOCAL\hvh 3.1.1 1
-
It is still slow when running the app on the physical server from the hyper-v (apps) server.
I have put the application on a directory on the physical server and shared that out for testing. More to come...
-
I gave the wrong command.
Get-SmbServerConfiguration
This one will tell you what SMB versions you have enabled for serving up shares. Only needed on the server side. -
@dashrender said in Network setup - Hyper-V:
I gave the wrong command.
Get-SmbServerConfiguration
This one will tell you what SMB versions you have enabled for serving up shares. Only needed on the server side.Physical or virtual or both?
-
@ccwtech said in Network setup - Hyper-V:
Get-SmbServerConfiguration
This is from the hyperv/apps server:
AnnounceComment :
AnnounceServer : False
AsynchronousCredits : 512
AuditSmb1Access : False
AutoDisconnectTimeout : 15
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 0
DurableHandleV2TimeoutInSeconds : 180
EnableAuthenticateUserSharing : False
EnableDownlevelTimewarp : False
EnableForcedLogoff : True
EnableLeasing : True
EnableMultiChannel : True
EnableOplocks : False
EnableSecuritySignature : False
EnableSMB1Protocol : True
EnableSMB2Protocol : True
EnableStrictNameChecking : True
EncryptData : False
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes : HydraLsPipe,TermServLicensing
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RejectUnencryptedAccess : True
RequireSecuritySignature : False
ServerHidden : True
Smb2CreditsMax : 8192
Smb2CreditsMin : 512
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True -
@ccwtech said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
I gave the wrong command.
Get-SmbServerConfiguration
This one will tell you what SMB versions you have enabled for serving up shares. Only needed on the server side.Physical or virtual or both?
both, since you're now testing both.
Also, you can wrap each block of text with 3 tick marks ` before and after
to see it like this -
You're Hyper-V has SMB1 enabled
-
@dashrender said in Network setup - Hyper-V:
You're Hyper-V has SMB1 enabled
But Hyper-V shouldn't be involved in SMB communications.
-
Physical Server
AnnounceComment : AnnounceServer : False AsynchronousCredits : 512 AuditSmb1Access : False AutoDisconnectTimeout : 15 AutoShareServer : True AutoShareWorkstation : True CachedOpenLimit : 10 DurableHandleV2TimeoutInSeconds : 180 EnableAuthenticateUserSharing : False EnableDownlevelTimewarp : False EnableForcedLogoff : True EnableLeasing : True EnableMultiChannel : True EnableOplocks : True EnableSecuritySignature : False EnableSMB1Protocol : True EnableSMB2Protocol : True EnableStrictNameChecking : True EncryptData : False IrpStackSize : 15 KeepAliveTime : 2 MaxChannelPerSession : 32 MaxMpxCount : 50 MaxSessionPerConnection : 16384 MaxThreadsPerQueue : 20 MaxWorkItems : 1 NullSessionPipes : NullSessionShares : OplockBreakWait : 35 PendingClientTimeoutInSeconds : 120 RejectUnencryptedAccess : True RequireSecuritySignature : False ServerHidden : True Smb2CreditsMax : 8192 Smb2CreditsMin : 512 SmbServerNameHardeningLevel : 0 TreatHostAsStableStorage : False ValidateAliasNotCircular : True ValidateShareScope : True ValidateShareScopeNotAliased : True ValidateTargetName : True -
@scottalanmiller said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
You're Hyper-V has SMB1 enabled
But Hyper-V shouldn't be involved in SMB communications.
For the test it is.
-
@dashrender said in Network setup - Hyper-V:
@scottalanmiller said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
You're Hyper-V has SMB1 enabled
But Hyper-V shouldn't be involved in SMB communications.
For the test it is.
What is the test testing?
-
@scottalanmiller said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
@scottalanmiller said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
You're Hyper-V has SMB1 enabled
But Hyper-V shouldn't be involved in SMB communications.
For the test it is.
What is the test testing?
If an OS installed directly on the hardware doesn’t have the slowness issue when sharing over The network vs the vm on its vSwitch that does have the issue.
What I don’t know is.... if Hyper-V is installed, is the hosts traffic in any way different than if it didn’t have the hyper-v role added?
