Graphic/Measure/Identify Drawing Tools Are So Slow
I'm under the impression that VSW app performance is directly related to client-side hardware. Is there anything else that could contribute poor performance when using the sketching operations activated by graphic drawing, measurement, and identify tools?
I've been telling my client that dedicated graphics will help, but as they have yet to add a GPU to their VMs, I can't directly test this. I'm wondering if there is anything else that could hinder performance of drawing tools.
My client also said that many average viewers (all internal to the org) will not have dedicated GPUs so, I know any slowness we can not mitigate now will remain for these users.
Any suggestions are appreciated!
- Jack C.
-
Hi Jack Charde ,
I too have noticed significant performance disparity on my VSW viewers for users that have GPUs on their computers, versus users who do not have GPUs. My desktop computer performs great, but my laptop struggles to even load the viewers, and then performance when using the maps is less than optimal. Same thing for my users: my geologists and engineers who have GPUs in their machines have no issues, but folks in accounting and our land department who have run-of-the-mill laptops experience significant performance issues.
I was at lunch with a former colleague a few weeks ago whose production web environment is still on GVH, and one of the main reasons they have not shifted to VSW is because of the severe performance drop that they have seen in their test environment.
Is there any suggestions or input from anyone at VertiGIS Studio Support that might help improve performance for computers without GPU, or any insight on what future developments might be happening to address this issue?
Thanks,
Brian
0 -
I agree the documentation on GPU is lacking, would expect it here
https://docs.vertigisstudio.com/webviewer/latest/admin-help/client-requirements.html
0 -
Reading into that, it appears that it's not a VertiGIS limitation so much as it is an ESRI limitation. The frustrating thing is that I'm not trying to display anything 3-D or graphics intensive. Everything is simple 2-D features.
I did some quick Googling and the A.I. responses hinted that feature layers tend to be more affected than map layers, so that's something to test. Most of my maps utilize feature layers instead of map layers.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
3 commentaires