Right now the basic draw procedures immediately process the CPU side operations and transform the data to what will be uploaded to GPU. We can probably batch these operations on the CPU more efficiently by caching the CPU side primitives and operating on like kind primitives together (likely with significant SIMD).
Just need to make sure we do this in a way that maintains proper ordering.
Right now the basic draw procedures immediately process the CPU side operations and transform the data to what will be uploaded to GPU. We can probably batch these operations on the CPU more efficiently by caching the CPU side primitives and operating on like kind primitives together (likely with significant SIMD).
Just need to make sure we do this in a way that maintains proper ordering.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Right now the basic draw procedures immediately process the CPU side operations and transform the data to what will be uploaded to GPU. We can probably batch these operations on the CPU more efficiently by caching the CPU side primitives and operating on like kind primitives together (likely with significant SIMD).
Just need to make sure we do this in a way that maintains proper ordering.
This will probably be the same change in which we add multi-window support and move away from storing all draw caching globally.