bevy/benches/Cargo.toml

[package]
name = "benches"
version = "0.1.0"
edition = "2021"

[dev-dependencies]
criterion = "0.3"
bevy = { path = "../" }

[[bench]]
name = "system_stage"
path = "benches/bevy_ecs/stages.rs"
harness = false

[[bench]]
name = "commands"
path = "benches/bevy_ecs/commands.rs"
harness = false

[[bench]]
name = "world_get"
path = "benches/bevy_ecs/world_get.rs"
harness = false

[[bench]]
name = "iter"
path = "benches/bevy_tasks/iter.rs"
harness = false
move benches to separate crate to cut test/example build times 2020-09-08 20:30:44 +00:00			`[package]`
			`name = "benches"`
			`version = "0.1.0"`
Update to edition 2021 on master (#3028) Objective During work on #3009 I've found that not all jobs use actions-rs, and therefore, an previous version of Rust is used for them. So while compilation and other stuff can pass, checking markup and Android build may fail with compilation errors. Solution This PR adds `action-rs` for any job running cargo, and updates the edition to 2021. 2021-10-27 00:12:14 +00:00			`edition = "2021"`
move benches to separate crate to cut test/example build times 2020-09-08 20:30:44 +00:00
			`[dev-dependencies]`
			`criterion = "0.3"`
			`bevy = { path = "../" }`

Moved benchmarks to a single place (#1477) Closes #1472. 2021-02-19 22:11:00 +00:00			`[[bench]]`
			`name = "system_stage"`
			`path = "benches/bevy_ecs/stages.rs"`
			`harness = false`

`Commands` benchmarking (#2334) # Objective - Currently the `Commands` and `CommandQueue` have no performance testing. - As `Commands` are quite expensive due to the `Box<dyn Command>` allocated for each command, there should be perf tests for implementations that attempt to improve the performance. ## Solution - Add some benchmarking for `Commands` and `CommandQueue`. 2021-06-28 23:26:29 +00:00			`[[bench]]`
			`name = "commands"`
			`path = "benches/bevy_ecs/commands.rs"`
			`harness = false`

Inline world get (#2520) # Objective While looking at the code of `World`, I noticed two basic functions (`get` and `get_mut`) that are probably called a lot and with simple code that are not `inline` ## Solution - Add benchmark to check impact - Add `#[inline]` ``` group this pr main ----- ---- ---- world_entity/50000_entities 1.00 115.9±11.90µs ? ?/sec 1.71 198.5±29.54µs ? ?/sec world_get/50000_entities_SparseSet 1.00 409.9±46.96µs ? ?/sec 1.18 483.5±36.41µs ? ?/sec world_get/50000_entities_Table 1.00 391.3±29.83µs ? ?/sec 1.16 455.6±57.85µs ? ?/sec world_query_for_each/50000_entities_SparseSet 1.02 121.3±18.36µs ? ?/sec 1.00 119.4±13.88µs ? ?/sec world_query_for_each/50000_entities_Table 1.03 13.8±0.96µs ? ?/sec 1.00 13.3±0.54µs ? ?/sec world_query_get/50000_entities_SparseSet 1.00 666.9±54.36µs ? ?/sec 1.03 687.1±57.77µs ? ?/sec world_query_get/50000_entities_Table 1.01 584.4±55.12µs ? ?/sec 1.00 576.3±36.13µs ? ?/sec world_query_iter/50000_entities_SparseSet 1.01 169.7±19.50µs ? ?/sec 1.00 168.6±32.56µs ? ?/sec world_query_iter/50000_entities_Table 1.00 26.2±1.38µs ? ?/sec 1.91 50.0±4.40µs ? ?/sec ``` I didn't add benchmarks for the mutable path but I don't see how it could hurt to make it inline too... 2021-07-27 23:19:26 +00:00			`[[bench]]`
			`name = "world_get"`
			`path = "benches/bevy_ecs/world_get.rs"`
			`harness = false`

move benches to separate crate to cut test/example build times 2020-09-08 20:30:44 +00:00			`[[bench]]`
			`name = "iter"`
			`path = "benches/bevy_tasks/iter.rs"`
update dependencies (#470) 2020-09-10 19:54:24 +00:00			`harness = false`