-
Notifications
You must be signed in to change notification settings - Fork 687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rust: bump ohkami to v0.21 #8180
Conversation
rust/ohkami/Cargo.toml
Outdated
ohkami = { version = "0.20", features = ["rt_tokio"] } | ||
tokio = { version = "1", features = ["macros", "rt-multi-thread"] } | ||
ohkami = { version = "0.21", features = ["rt_tokio"] } | ||
nio = { version = "0.0" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is the idea of this 0.0 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I forgot to chage features
to ["rt_nio"]
from ["rt_tokio"]
.
I'm trying nio experimental runtime instead of tokio here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you then create okhami-nio and okhami-tokio ?
as we have for javascript with -bun and -deno
rust/ohkami/Cargo.toml
Outdated
ohkami = { version = "0.20", features = ["rt_tokio"] } | ||
tokio = { version = "1", features = ["macros", "rt-multi-thread"] } | ||
ohkami = { version = "0.21", features = ["rt_tokio"] } | ||
nio = { version = "0.0" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you then create okhami-nio and okhami-tokio ?
as we have for javascript with -bun and -deno
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
better to expose result for both runtimes, tokio
and nio
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
rust/ohkami-nio/Cargo.toml
Outdated
[profile.release] | ||
opt-level = 3 | ||
debug = false | ||
debug-assertions = false | ||
lto = true | ||
panic = "abort" | ||
incremental = false | ||
lto = true | ||
panic = "abort" | ||
codegen-units = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not needed 😛
compilation options are in rust/Dockerfile
what is codegen-units for ?
[profile.release] | ||
lto = true | ||
panic = "abort" | ||
codegen-units = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[profile.release] | |
lto = true | |
panic = "abort" | |
codegen-units = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They're quite standard optimizations for release
profile ( other rust frameworks do the same in their Cargo.toml
s, too )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now almost all rust/*
are using
[profile.release]
opt-level = 3
debug = false
debug-assertions = false
lto = true
panic = "abort"
incremental = false
codegen-units = 1
rpath = false
strip = false
( see their Cargo.toml
s )
but actually other than lto = true
, panic = "abort"
and codegen-units = 1
are default configuration of release
profile, so I just set them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed them in current branch, from advice of @msrd0. The compilation step is
cargo build --release \
--config 'profile.release.lto=true' \
--config 'profile.release.panic="abort"' \
--config 'profile.release.codegen-units=1'
No description provided.