Sage 100

Slow performance on VM with 2019 and windows 10.

 You may be seeing this due to Receive Segment Coalescing (RSC). In short, RSC is TCP segment aggregation that combines segments in order to process larger segments versus multiple small segments for efficiency. This was introduced as a default configuration change for Windows Server 2019 and has been the source of issues similar to yours in other environments.

1. You can disable a client's RSC for IPv4 traffic using PowerShell: Disable-NetAdapterRsc -Name $nic -IPv4.
2. You can check a Hyper-V vSwitch's current RSC status using PowerShell: Get-VMSwitch -Name $vSwitch | Select *RSC*.
3. You can disable a Hyper-V vSwitch's RSC in full using PowerShell: Set-VMSwitch -Name $vSwitch -EnableSoftwareRsc:$FALSE. This will not impact existing vSwitch connections.

Slow performance on VM with 2019 and windows 10.

 You may be seeing this due to Receive Segment Coalescing (RSC). In short, RSC is TCP segment aggregation that combines segments in order to process larger segments versus multiple small segments for efficiency. This was introduced as a default configuration change for Windows Server 2019 and has been the source of issues similar to yours in other environments.

1. You can disable a client's RSC for IPv4 traffic using PowerShell: Disable-NetAdapterRsc -Name $nic -IPv4.
2. You can check a Hyper-V vSwitch's current RSC status using PowerShell: Get-VMSwitch -Name $vSwitch | Select *RSC*.
3. You can disable a Hyper-V vSwitch's RSC in full using PowerShell: Set-VMSwitch -Name $vSwitch -EnableSoftwareRsc:$FALSE. This will not impact existing vSwitch connections.

Slow performance on VM with 2019 and windows 10.

 You may be seeing this due to Receive Segment Coalescing (RSC). In short, RSC is TCP segment aggregation that combines segments in order to process larger segments versus multiple small segments for efficiency. This was introduced as a default configuration change for Windows Server 2019 and has been the source of issues similar to yours in other environments.

1. You can disable a client's RSC for IPv4 traffic using PowerShell: Disable-NetAdapterRsc -Name $nic -IPv4.
2. You can check a Hyper-V vSwitch's current RSC status using PowerShell: Get-VMSwitch -Name $vSwitch | Select *RSC*.
3. You can disable a Hyper-V vSwitch's RSC in full using PowerShell: Set-VMSwitch -Name $vSwitch -EnableSoftwareRsc:$FALSE. This will not impact existing vSwitch connections.

Slow performance on VM with 2019 and windows 10.

 You may be seeing this due to Receive Segment Coalescing (RSC). In short, RSC is TCP segment aggregation that combines segments in order to process larger segments versus multiple small segments for efficiency. This was introduced as a default configuration change for Windows Server 2019 and has been the source of issues similar to yours in other environments.

1. You can disable a client's RSC for IPv4 traffic using PowerShell: Disable-NetAdapterRsc -Name $nic -IPv4.
2. You can check a Hyper-V vSwitch's current RSC status using PowerShell: Get-VMSwitch -Name $vSwitch | Select *RSC*.
3. You can disable a Hyper-V vSwitch's RSC in full using PowerShell: Set-VMSwitch -Name $vSwitch -EnableSoftwareRsc:$FALSE. This will not impact existing vSwitch connections.

Slow performance on VM with 2019 and windows 10.

 You may be seeing this due to Receive Segment Coalescing (RSC). In short, RSC is TCP segment aggregation that combines segments in order to process larger segments versus multiple small segments for efficiency. This was introduced as a default configuration change for Windows Server 2019 and has been the source of issues similar to yours in other environments.

1. You can disable a client's RSC for IPv4 traffic using PowerShell: Disable-NetAdapterRsc -Name $nic -IPv4.
2. You can check a Hyper-V vSwitch's current RSC status using PowerShell: Get-VMSwitch -Name $vSwitch | Select *RSC*.
3. You can disable a Hyper-V vSwitch's RSC in full using PowerShell: Set-VMSwitch -Name $vSwitch -EnableSoftwareRsc:$FALSE. This will not impact existing vSwitch connections.

I'm going to bring this back to life, since I stirred it up in another thread earlier this week.  Is there a Sage whitepaper on 64-bit Sage?  It is as if there's no information published about this other than the birth announcement with 2021's release.  I have customers with larger Sage installations with performance issues and I would like to know if changing to 64-bit Sage has proven to have any performance advantages over 32-bit, or if there is any difference at all.  The very few discussions I've been able to find seem to point to the same result - no difference.  

Slow performance on VM with 2019 and windows 10.

 You may be seeing this due to Receive Segment Coalescing (RSC). In short, RSC is TCP segment aggregation that combines segments in order to process larger segments versus multiple small segments for efficiency. This was introduced as a default configuration change for Windows Server 2019 and has been the source of issues similar to yours in other environments.

1. You can disable a client's RSC for IPv4 traffic using PowerShell: Disable-NetAdapterRsc -Name $nic -IPv4.
2. You can check a Hyper-V vSwitch's current RSC status using PowerShell: Get-VMSwitch -Name $vSwitch | Select *RSC*.
3. You can disable a Hyper-V vSwitch's RSC in full using PowerShell: Set-VMSwitch -Name $vSwitch -EnableSoftwareRsc:$FALSE. This will not impact existing vSwitch connections.