-
Notifications
You must be signed in to change notification settings - Fork 260
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
core: Replace epoch deadline with yield #1684
base: main
Are you sure you want to change the base?
Conversation
/// details of the system's thread scheduler. | ||
/// | ||
/// See [`wasmtime::Store::set_epoch_deadline`](https://docs.rs/wasmtime/latest/wasmtime/struct.Store.html#method.set_epoch_deadline). | ||
pub fn set_deadline(&mut self, deadline: Instant) { |
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.
Based on some searching I'm reasonably confident that this method isn't being used anywhere (public).
crates/core/src/lib.rs
Outdated
@@ -37,7 +37,7 @@ pub use io::OutputBuffer; | |||
pub use store::{Store, StoreBuilder, Wasi, WasiVersion}; | |||
|
|||
/// The default [`EngineBuilder::epoch_tick_interval`]. | |||
pub const DEFAULT_EPOCH_TICK_INTERVAL: Duration = Duration::from_millis(10); | |||
pub const DEFAULT_EPOCH_TICK_INTERVAL: Duration = Duration::from_micros(100); |
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.
This arbitrarily updates the original arbitrary value, which "felt too slow" to me. 🤷
@lann what's the state of this? I thought this had already been merged. |
Uhh I think I lost track of this back when e2e tests were broken for a while. Will refresh. |
7d907df
to
7bae4a1
Compare
@lann did this once again go stale? |
Yep, but it could still be reviewed and then I could just merge it after the next rebase 🙂 |
With async yielding, instance execution can be implemented by dropping the async call future, with e.g. tokio::time::timeout. Signed-off-by: Lann Martin <[email protected]>
Sorry I'm a year and a half late on this; is it still relevant? |
Oof I'll have to set a reminder to come back and check in the new year 😬 |
With async yielding, instance execution can be implemented by dropping the async call future, with e.g. tokio::time::timeout.