Optimization opportunities (tracking issue) · emilk/egui#1196

(2 comments) (7 reactions) (0 assignees)Rust (29,051 stars) (2,037 forks)batch import

help wantedperformance

Description

There is a lot of room for improvements to the CPU usage of egui. Here are some things worth investigating:

Try different hash algorithms for Id, FontCache and others.
Precompute vertices for circles and rounded corners in epaint::Tessellator constructor (https://github.com/emilk/egui/pull/1547)
Paint small filled circles using textured rects (by adding a few low-radius circles to the font atlas) (https://github.com/emilk/egui/pull/1616)
Run egui with a proper profiler and see what pops up
- Try https://github.com/mstange/perfrecord
https://github.com/emilk/egui/issues/1098
eframe/native: run App::update and the rendering in different threads
Output a single veretex buffer and index buffer instead of Vec<ClippedPrimitive>
emilk/egui#3862
emilk/egui_plot#18,

Any PR should come with a benchmark.

Tech stack: rust
Domain: performance
Issue type: research
Difficulty: 4
Estimated time: over 1 week
Activity status: stale
Clarity: mostly clear
Prerequisites: Rustegui codebaseprofiling tools
Newbie friendliness: 20
Research direction: This tracking issue lists several optimization opportunities for egui. Newcomers can investigate open items such as running a profiler on egui (see issue #1098) or outputting a single vertex/index buffer. Any contribution should include benchmarks to demonstrate improvement. The codebase is primarily in Rust, and changes likely involve the `epaint` crate and `eframe/native` backend.