iced-rs/iced

Perform benchmarks

Open

#7 创建于 2019年9月5日

在 GitHub 查看
 (5 评论) (0 反应) (0 负责人)Rust (30,491 star) (1,572 fork)batch import
help wantedimprovementperformance

描述

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!

贡献者指南

技术栈
rust
领域
performance
议题类型
performance
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic Rust knowledgeFamiliarity with benchmarking (e.g. criterion)
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
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.