iced-rs/iced

Perform benchmarks

Open

#7 opened on Sep 5, 2019

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

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

Tech stack
rust
Domain
performance
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic Rust knowledgeFamiliarity with benchmarking (e.g. criterion)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
This issue requests adding benchmarks for the UserInterface struct's build, update, and draw methods. The most expensive operation is UserInterface::build, so start with that. Look at the existing codebase to understand how UserInterface is implemented (likely in src/user interface.rs or similar). Use the criterion crate for benchmarking. Check if there are existing tests or benchmarks in the repository (e.g., benches/ directory). Also review comments on the issue for any previous discussion about approach. Focus on creating a benchmark harness that measures the time of these methods with various widget counts.