Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Recover some headroom under the Memory.Footprint ceiling #8247

Closed
anandthakker opened this issue Mar 1, 2017 · 1 comment · Fixed by #9003
Closed

Recover some headroom under the Memory.Footprint ceiling #8247

anandthakker opened this issue Mar 1, 2017 · 1 comment · Fixed by #9003
Assignees
@jfirebaugh
Labels
Core The cross-platform C++ core, aka mbgl performance Speed, stability, CPU usage, memory usage, or power usage

Comments

@anandthakker
Copy link
Contributor

#7939 brought us just under the vectorFootprint ceiling in the Memory.Footprint test -- close enough that measurement variance is now causing intermittent failures. Better than raising the ceiling would be to find an optimization that offsets the necessary increase incurred by #7939.
@anandthakker anandthakker self-assigned this Mar 1, 2017
@anandthakker anandthakker added Core The cross-platform C++ core, aka mbgl performance Speed, stability, CPU usage, memory usage, or power usage labels Mar 1, 2017
@jfirebaugh jfirebaugh mentioned this issue Mar 8, 2017
Merged
@anandthakker
Copy link
Contributor Author

#8320 slightly--and temporarily--increases the memory ceiling to keep travis happy until we can tackle this. Once we've recovered some room, we should revert that increase.

cc @jfirebaugh

@jfirebaugh jfirebaugh mentioned this issue May 19, 2017
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jfirebaugh jfirebaugh

Labels
Core The cross-platform C++ core, aka mbgl performance Speed, stability, CPU usage, memory usage, or power usage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[core] Don't use a separate SpriteAtlas for annotation images mapbox/mapbox-gl-native
2 participants
@jfirebaugh @anandthakker