Optimization opportunities (tracking issue)

(2 commenti) (7 reazioni) (0 assegnatari)Rust (2101 fork)batch import

help wantedperformance

Metriche repository

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.

Direzione di ricerca: Esegui un profiler sulle applicazioni egui e identifica i colli di bottiglia nell'uso della CPU. Considera il parallelismo dei thread e l'unione dei buffer.
Tech stack: rust
Dominio: frontend
Tipo issue: Performance
Difficoltà: 4
Tempo stimato: Oltre 1 settimana
Stato attività: Attiva
Chiarezza: Chiara
Prerequisiti: Rust
Adatta ai principianti: 20