We retired a 2008R2 server and moved Adagio to a virtual machine (2016Std on Hyperv2019). The new server has 24 cores and 48G of ram with SSD hard drives. We have 16gb of RAM and 4 cores assigned to the Adagio VM. AV is also disabled for Adagio on the server and the workstations, but performance is poor - even stand alone on the server so network shouldn't be the cause.

I have a system snap shot which we'd like someone to take a look at.

Hi,
You are asking for expertise that is not normally available on a free chat forum. Your hardware description details look more than fine for Adagio on 2016Std.

Check your speed logging directly on onto the server and run Adagio on the server to isolate and eliminate the network element.

Try running on the server with UNC path mappings instead of logical drive mappings. We have seen situations that cause laggard speed issues where Adagio spends time trying to resolve pathing issues on logical drives.

If you want us to really take a look at this, $250 per hour with a minimum charge of $350. Our team can solve this issue or no charge.

Best,
Brian

Hi,
You are asking for expertise that is not normally available on a free chat forum. Your hardware description details look more than fine for Adagio on 2016Std.

Check your speed logging directly on onto the server and run Adagio on the server to isolate and eliminate the network element.

Try running on the server with UNC path mappings instead of logical drive mappings. We have seen situations that cause laggard speed issues where Adagio spends time trying to resolve pathing issues on logical drives.

If you want us to really take a look at this, $250 per hour with a minimum charge of $350. Our team can solve this issue or no charge.

Best,
Brian

Epilogue:??
We connected to the client site and confirmed that hardware settings were reasonable (and good) and but made some adjustments to the NIC Devices settings. However, the real reason for the speed performance degradation which we confirmed was a mixture of logical mapped drives and UNC paths, of Adagio programs and data files. We did tests before and after the changes which we made. and the impact was immediate.

We confirmed that the resolution was changing the pathing strings to complete compliance with UNC Path mapping.

We further edited the Softrak entries in the registry to correct settings that appear related to different updates depending on the sequence that the module upgrades were installed.

We further edited string corrections in the Adagio module ini files and matched the revised UNC path registry settings.

These instructions should be part of your best Adagio practices setup and module configurations.

Best,
Brian

This is good advice, Brian - Thanks.
Especially for new installs, sounds like we should not bother with mapped drives, and only go with UNC.