Skip to content
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

Color and Pickability Schema for Improved RAM and VRAM Usage #773

Open
thkruz opened this issue Oct 16, 2023 · 0 comments
Open

Color and Pickability Schema for Improved RAM and VRAM Usage #773

thkruz opened this issue Oct 16, 2023 · 0 comments
Assignees
Milestone

Comments

@thkruz
Copy link
Owner

thkruz commented Oct 16, 2023

User Story

  • As a developer of the color scheme manager
  • I want to optimize the storage of object colors
  • So that memory usage is reduced and performance is improved.

Acceptance Criteria

  • Given an object with color and pickability data

  • When I assign a color and pickability to it

  • Then it should store only a single int8 corresponding to a uniform, instead of multiple numbers.

  • Given a stored int8 corresponding to a color and pickability

  • When I want to retrieve or utilize this data

  • Then the system should accurately interpret this int8 and provide the correct rgba and pickability properties.

  • Given a user changes the default color values

  • When the application updates the uniform

  • Then it should reflect the updated color and pickability accurately.

Commentary

Currently, we store colors as arrays for rgba values, and we have a separate int8 for pickability. This proposal suggests a more efficient approach by condensing the storage into a single int8, which corresponds to a uniform passed to the GPU. This uniform will contain the rgba component and pickability status. For instance, 1 could mean [255,0,0,1] and pickable, while 2 indicates [255,0,0,1] and NOT pickable. By implementing this, we can greatly optimize memory usage and potentially enhance performance.

@thkruz thkruz added this to the Next Up milestone Oct 16, 2023
@thkruz thkruz self-assigned this Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant