Very poor performance on high resolution (5k)

I have a viewer in which I navigate using fitBounds. It behaves perfectly until I put it on a 5k screen, then it becomes very laggy, it seems to take very long to load. Any idea why does it become really laggy and how could I avoid this?

[iangilman]

@differenceclouds You should be able to disable most animation by using animationTime: 0 in your viewer options.

Does Safari have an FPS meter like Chrome does? I’d love to hear what you find on the performance front.

[jetic83]

I also experienced some slowniness on larger screens, but it is really a complex question. Some sources of perfomance issues can be:

• the size itself needs more tiles to be loaded. But a browser only allows 4 or 6 concurrent connections to one server. So some tiles start to have to wait for download. You can see that well with Chrome‘s network inspection.
• overlays on OSD (also e.g. fabricjs) slow down at many objects (many can be a low number, such as 10, 20, 30). But a larger screen displays more objects. Are your divs overlays?

Profiling is a good way to identify what is exactly slow. WebGL really sounds highly interesting. But it seems to be complicated too, otherwise people would have implemented it already.

I am in the stage where I want to optimize the experience too, but it is surprisingly smooth on a fullscreen Surface Studio, Edge, win 10, while it is much slower on a Desktop machine, Chrome, win 7.