You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2022. It is now read-only.
Rust is notorious for slow compile times so i suspect many devs use debug builds most of the time. If an ECS is fast with optimizations but unusably slow without them, it would be good to find out early. For example, in my unscientific expriments, hecs and legion were about the same in release mode but legion was several times slower is debug mode (don't have exact numbers anymore).
I suggest this bench suite should test 3 configurations:
Everything in release mode (this is what it does currently I believe)
Everything in debug mode
Deps (which in normal usage change infrequently) in release mode but the main crate (typically the gamelogic which changes often) in debug mode - this is what macroquad suggests (expand Tips):
[profile.dev.package.'*']
opt-level = 3
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Rust is notorious for slow compile times so i suspect many devs use debug builds most of the time. If an ECS is fast with optimizations but unusably slow without them, it would be good to find out early. For example, in my unscientific expriments, hecs and legion were about the same in release mode but legion was several times slower is debug mode (don't have exact numbers anymore).
I suggest this bench suite should test 3 configurations:
The text was updated successfully, but these errors were encountered: