-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too slow on Chrome Mobile #1226
Comments
By the way, I was testing with a Moto G 2nd edition. |
Is it too slow but working, or just not interactive? If the latter, we have that coming in #949. |
Well, this is actually about it being slow. It's rendering at about 11 fps on my chrome mobile on a Moto G 2nd edition. The scroll also has issues, but I'm talking about the speed. |
I think this is a hardware limitation, and not something we can easily fix on the GL JS side. |
It's not necessarily a hardware limitation; the Moto G 2 renders just fine with the native Android app; so it's likely that the slowdown is either from the discrepancies between GL/JS and GL/Native (tessellation), V8/JavaScript, or the Chrome WebGL bindings, or a combination thereof. |
Yeah, I meant hardware or WebGL implementation limitation. It may be improved in future with things like #682, but there's no sense keeping this as a separate open ticket. |
I tested with the default style map and it is too slow: https://www.mapbox.com/mapbox-gl-styles/#14.45/-23.5381/-46.6551
I also made a visualization using version 0.7 and leaflet. It broke down rendering São Paulo, I couldn't move the map.
The text was updated successfully, but these errors were encountered: