Optimization opportunities (tracking issue)

(2 commentaires) (7 réactions) (0 personne assignée)Rust (2 104 forks)batch import

help wantedperformance

Métriques du dépôt

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.

Direction de recherche: Exécutez un profileur sur les applications egui et identifiez les points chauds de l'utilisation du CPU. Envisagez le parallélisme des threads et la fusion des tampons.
Stack technique: rust
Domaine: frontend
Type d'issue: Performance
Difficulté: 4
Temps estimé: Plus d'une semaine
Statut d'activité: Active
Clarté: Claire
Prérequis: Rust
Accessibilité débutant: 20