-
Notifications
You must be signed in to change notification settings - Fork 86
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
scx_stats: Drop sched-ext namespace #573
Conversation
Signed-off-by: Piotr Gorski <lucjan.lucjanov@gmail.com>
ba14d33
to
a860997
Compare
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.
Left a couple of comments (feel free to ignore), but overall looks good!
services/README.md
Outdated
|
||
``` | ||
journalctl --namespace=sched-ext --disk-usage | ||
scx_SCHEDNAME --monitor X |
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.
Maybe change to --monitor SEC
here to make it more clear that the argument defines the interval (in seconds) to print the output.
services/README.md
Outdated
``` | ||
|
||
X - for example 1 - this will print the output every second | ||
|
||
|
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.
And maybe add a real example, like:
scx_bpfland --monitor 0.5
To make it even more clear and to show that it also supports numbers with decimals.
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 agree adding real examples would be nicer here.
For example, in case of LAVD, its monitoring option is a bit different from the others.
/// Run in monitoring mode. Show the specified number of scheduling
/// samples every second.
#[clap(long)]
monitor_sched_samples: Option<u64>,
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 take a look, please?
a860997
to
0464a1a
Compare
@arighi I don't like to ignore wise advice. Is it better now? |
Maybe we should move the log information to a separate README or write information about it in the main one? |
Hm... maybe the monitor info should go in the main README, since they're affecting everyone and not only those that are running the schedulers via systemd. |
Let me know if the corrected examples are good and I will send the revisions to README. |
Signed-off-by: Piotr Gorski <lucjan.lucjanov@gmail.com>
c4e6a7f
to
c338363
Compare
README.md
Outdated
- scx_rustland | ||
|
||
``` | ||
❯ run0 scx_rustland --monitor 5 |
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.
Why using here run0?
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.
Removed
for example 0.5 - this will print the output every half a second | ||
|
||
``` | ||
scx_bpfland --monitor 0.5 |
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.
Personally would remove this part with the "for example 0.5". This just makes the README bigger with not much value
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 think such an example can stay to show exactly what it is about, but if more people think the same, I will remove it.
README.md
Outdated
kick_greedy_cpus=f | ||
NODE[00] load= 0.17 imbal= +0.00 delta= +0.00 | ||
DOM[00] load= 0.17 imbal= +0.00 delta= +0.00 | ||
###### Thu, 29 Aug 2024 14:42:42 +0200, load balance @ -1268.9ms ###### |
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.
Would also reduce here the logs, so that the README is not too much filled with logs.
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.
Fixed
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.
Do we really need to explain from every supported scx scheduler how to use monitor?
I think you could write, which are the supported schedulers and bring one example. instead of showing of every scheduler a example.
@@ -344,6 +344,87 @@ $ cargo install scx_rusty | |||
|
|||
and `scx_rusty` will be built and installed as `~/.cargo/bin/scx_rusty`. | |||
|
|||
## Checking scx_stats | |||
|
|||
- To check the scheduler statistics, use the |
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.
How about something like:
Most schedulers implement --monitor $INTERVAL
which fetches and shows the detailed statistics from the running scheduler. Note that this does not launch the scheduler. The monitoring instance only shows the statistics. Some schedulers may implement different or multiple monitoring options. Refer to --help
of each scheduler for details. Most schedulers also accept --stats $INTERVAL
to print the statistics directly from the scheduling instance.
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.
Updated, could you take a look now @htejun
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.
Maybe use "statistics" consistently? Schedulers do print out logs like info and warning messages. It just doesn't print out detailed statistics by default.
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.
Done @htejun
c338363
to
729a8cc
Compare
5158d14
to
ef28c19
Compare
@multics69 asked about examples. |
Signed-off-by: Piotr Gorski <lucjan.lucjanov@gmail.com>
ef28c19
to
cd8b73a
Compare
It looks like we have enough approvals and with scx_rustland also converted to use scx_stats I think we can safely apply this change. |
Since scx_stats has been implemented, namespace is already redundant.