Google Chrome vs Microsft Edge for Communicator Web Viewing

We have our products built on top of Communicator for web-based visualisation of federated CAD and BIM models. Is it possible that graphics performance on Microsoft Edge is slower than on Chrome? Some of our end users have observed this and have requested performance optimisations specifically for Edge.

Before we do any investigation by comparing against any benchmark, do you have any known analysis already done for communicator around this topic and any suggestions.

Hello,

We don’t have specific reports of slower performance on Microsoft Edge relative to Google Chrome. That said, there may be some variability in their respective performance as the browsers are from different companies.

In my research, you can try changing the following experimental graphics flags. Type edge://flags in the address bar and change:

Flag Name Recommended Setting What it Does
Choose ANGLE graphics backend D3D11 or OpenGL Changes the underlying API Edge uses to talk to your GPU. D3D11 is standard for Windows, but OpenGL or Vulkan can sometimes offer better 3D performance in specific WebGL apps.
GPU rasterization Enabled Forces the GPU to handle the heavy lifting of rendering website content (pixels/textures) instead of the CPU.
Override software rendering list Enabled Forces Edge to use hardware acceleration even if your specific GPU or driver version is blacklisted as unstable. Use with caution.
Zero-copy rasterizer Enabled Reduces memory usage by writing raster threads directly to GPU memory, which can reduce lag in 3D environments.

Also, you can try different values for setMinimumFramerate which is a tradeoff between FPS and model culling.