nmwsharp / nmwsharp/polyscope

Performance optimizations for geometric data buffers

Open
#103 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
2.2k
Forks
242
Avg merge
11m
Merged PRs (30d)
1

Description

Two changes which will dramatically improve performance relating to geometric buffers (e.g. vertex positions).

  • Use a shared buffer on the GPU, instead of storing many redundant copies for each quantity
  • Don't call refresh() when geometry is updated; call some simpler function that does less work.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the geometric buffer and geometry update paths referenced in the issue, then inspect how GPU buffers are currently duplicated and how refresh() is invoked. Done means sharing one GPU buffer for each relevant quantity and replacing geometry updates with a lighter operation without changing viewer behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics, performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.