mab122
/
radicle-heartwood-lfs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

node/reactor: Introduce `LAG_TIMEOUT` 

Since the service performs further I/O (e.g. uses SQLite), it can keep
the reactor runtime thread busy for long periods. Emit a warning if that
is the case.

100 ms is quite relaxed, this is to only catch severe cases and avoid
spamming the log.
This commit is contained in:
Lorenz Leutgeb 2025-10-18 01:29:38 +02:00 committed by Fintan Halpenny
parent ae06111e07
commit 057edf55b8
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
crates/radicle-node/src/reactor.rs
View File

@ -34,6 +34,12 @@ const SECONDS_IN_AN_HOUR: u64 = 60 * 60;
/// Maximum amount of time to wait for I/O. /// Maximum amount of time to wait for I/O.
const WAIT_TIMEOUT: Duration = Duration::from_secs(SECONDS_IN_AN_HOUR); const WAIT_TIMEOUT: Duration = Duration::from_secs(SECONDS_IN_AN_HOUR);
/// Maximum duration to accept the service to spend handling events (and errors,
/// ticking, etc.) without warning. Set to log whenever the service becomes so
/// is so slow to respond that it would not be able to handle at least 10
/// "requests" per second, i.e. `1s / 10 = 100ms`.
const LAG_TIMEOUT: Duration = Duration::from_millis(100);
/// A resource which can be managed by the reactor. /// A resource which can be managed by the reactor.
pub trait EventHandler { pub trait EventHandler {
/// The type of reactions which this resource may generate upon receiving /// The type of reactions which this resource may generate upon receiving
@ -423,6 +429,11 @@ impl<H: ReactionHandler> Runtime<H> {
} }
} }
let duration = Instant::now().duration_since(tick);
if duration > LAG_TIMEOUT {
log::warn!(target: "reactor", "Service was busy {:?} which exceeds the timeout of {:?}", duration, LAG_TIMEOUT);
}
self.handle_actions(tick); self.handle_actions(tick);
} }
} }