-
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
Don't serialize SymbolFeature as part of SymbolInstance #7012
Labels
performance ⚡
Speed, stability, CPU usage, memory usage, or power usage
Comments
This showed up as a significant part of the size of the JSON we transfer in: #7011. |
ChrisLoer
added a commit
that referenced
this issue
Jul 23, 2018
Fixes issue #7012. This data is expensive to serialize and isn't even being used.
6 tasks
mourner
pushed a commit
that referenced
this issue
Jul 23, 2018
Fixes issue #7012. This data is expensive to serialize and isn't even being used.
Fixed in #7013. |
pirxpilot
pushed a commit
to pirxpilot/mapbox-gl-js
that referenced
this issue
Sep 6, 2018
Fixes issue mapbox#7012. This data is expensive to serialize and isn't even being used.
pirxpilot
pushed a commit
to pirxpilot/mapbox-gl-js
that referenced
this issue
Sep 11, 2018
Fixes issue mapbox#7012. This data is expensive to serialize and isn't even being used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we transfer a symbol bucket from the workers to the foreground, we include a copy of the source feature for each
SymbolInstance
we generate:mapbox-gl-js/src/data/bucket/symbol_bucket.js
Lines 76 to 77 in 83b147b
These features are bulky and expensive to transfer, and as far as I know they're unused on the foreground. If we need access to the source feature on the foreground, we can use the "feature index" to look the feature up directly in the source data for the tile.
/cc @anandthakker @ansis @mourner
The text was updated successfully, but these errors were encountered: