3 ms·
Hmm that might also be contributing to dogshit Firefox performance on a web app of mine, I'm using that to store and fetch map tiles. Though that's all async so
by moffkalast 1y ago
Hmm that might also be contributing to dogshit Firefox performance on a web app of mine, I'm using that to store and fetch map tiles. Though that's all async so it shouldn't really matter in terms of rendering aside from having to wait a bit longer to retrieve.
But it already lags like fuck even without that part running or anything much at all, while being buttersmooth on Chrome almost regardless of how much I load up rendering. It infuriates me to hell because there is no optimization I can make to get equal or even usable performance.
- jesup 1y agoWhat's the webapp? Can you file a bug in Bugzilla in Core::Performance with steps to reproduce? Can you take a profile? https://profiler.firefox.com https://profiler.firefox.com You can attach it to the bug, or drop it in #perf on https://chat.mozilla.org https://chat.mozilla.org (Matrix)