-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Merge multiple vertex or elements buffers #207
Labels
performance ⚡
Speed, stability, CPU usage, memory usage, or power usage
Comments
Did @ansis rewrite this recently? |
This is still relevant, and should be changed to match what native does. |
bensleveritt
pushed a commit
to bensleveritt/mapbox-gl-js
that referenced
this issue
Oct 24, 2016
Don't ignore dist/mapbox-gl-draw.js on npm publish
Not sure how relevant this ticket is given that we use VBOs in most situations anyway. |
I've implemented this and will have a PR pending #3439. Not needing to keep track of multiple array/buffer groups per bucket is a nice code simplification. |
👍 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we create separate vertex/elements buffers when the vertex buffer reaches an item count of 65536. However, we could just continue in the same buffer and just reset the vertexAttribPointer to start indexing the buffer at a later position. That way, we'd have fewer buffer switches and fewer buffer transfer operations overall.
The text was updated successfully, but these errors were encountered: