iced-rs/iced

Perform benchmarks

Open

#7 opened on Sep 5, 2019

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Rust (1,572 forks)batch import
help wantedimprovementperformance

Repository metrics

Stars
 (30,491 stars)
PR merge metrics
 (Avg merge 24d 11h) (11 merged PRs in 30d)

Description

As mentioned in #4, in order to avoid performance regressions, it would be great to run some benchmarks on the different parts of the API.

The most expensive operation is clearly UserInterface::build. This will be the main focus for many of the optimizations we will implement in the future. We should benchmark this first.

UserInterface::update and UserInterface::draw will also get slower the more widgets and events a user interface has to handle. It would be great to have some numbers!

Contributor guide

Research direction
Set up a benchmarking framework (e.g., Criterion) and create benchmarks for UserInterface::build, UserInterface::update, and UserInterface::draw. Analyze the existing code to understand the operations being benchmarked.
Tech stack
rust
Domain
frontend
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65