NXG 3.0.2 is very slow

[fblerg]

Hi MaximeR,

OK, thanks for changing those configurations and testing. You are correct; the forum poster was using VMWare. Any chance to test on your physical machine?

Correct, the release version of LabVIEW NXG 3.1 should be available in the near future. Please let us know if you have any thoughts on 3.1. 

Thanks,

Frank

[MaximeR]

Hi,

I isntalled NXG 3.0.2 on my computer for Test. I tried wih Win10 x64.

Computer is HP 6570b, with 8GB of memory and, same SSD that the one running my VM, i5-3320M. No dedicated graphic card.

Launching NXG is faster. Between 1 min to 1min 30s.

Create New VI is also faster.

Switching from diagram to FP is more reactiv.

It's much more better than inside VM, but i'm still feeling some latency on clic.

I also need to check if I have all the same module installe on my physical machine but it take a lot of time.

For all our developments, we are using VM to be as possible in the same configuration of our customers. We have a a lot of different configuration, and using VM is the best way for us. I think that NXG must be more reactiv in any case and you need to have a look on using it inside VM. I know that a lot of NI Partners are using VM. Of course, we know that we lost performance by using VM (10 to 20% is acceptable), but for the moment, it's not usable.

Visual Studio is running well inside VMs for Example, and my LabVIEW 2018 is running well to. So please, do something.

Best regards.

[fblerg]

Hi Maxime,

Thanks for testing on your physical machine and providing this valuable feedback. I agree that developing on a VM is important use case, which we will need investigate further. I will setup a test VM with similar specs (Windows 10 x64, SSD, 4 GB, 2-Core CPU), do performance profiling with this setup, and see what we could do to improve this use case. 

For some context, I am on the NXG Performance team, and our focus is improving NXG performance. For the upcoming release, our focus has been on Project Loading time, Time to Editing a VI, and Time to Run a VI (with a compiled code cache). Your comments have re-enforced the need to account for developing on minimum spec VMs, which is common for general LabVIEW development. 

Having your feedback is key to improving performance, so thank you for taking the time to test and provide your thoughts.

Thanks,

Frank