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
I would assume that setting tokio to the current_thread runtime flavour would probably be okay for the project, and also seems like a simpler/less resource consuming default?
The text was updated successfully, but these errors were encountered:
My 2 cents here: if the number of threads is important in the context of a highly solicited server, on simpler setups it is overkill; perhaps adding a config parameter / startup flag would be the best response for both situations ...
I'd be fine with configurable too, but I would say the default should be single thread as the majority of users of this I assume will be clients. If you're running an ntpd-rs server then it's easy to bump this up if needed.
Hi there,
In https://github.com/pendulum-project/ntpd-rs/blob/main/ntpd/bin/ntp-daemon.rs#L5 you are using tokio::main which activates the multi-thread scheduler. On my xeon server with 24 threads, this means that I have ntpd-rs with 24 idle threads.
I would assume that setting tokio to the current_thread runtime flavour would probably be okay for the project, and also seems like a simpler/less resource consuming default?
The text was updated successfully, but these errors were encountered: