Re: [PATCH V3 1/2] sched: Reduce the default slice to avoid tasks getting an extra tick

[zihan zhou]

Thank you for your reply! I don't mind at all, and I'm also sorry for the
slow response due to too many things lately.

> Hello Zhou,
> 
> Sorry this slipped past me.

Thank you very much for your guidance! I realize that without a good
benchmark, it is impossible to truly do a good job in scheduling. I will
try my best to make time to do this well.

> We use selective benchmarks from LKP: https://github.com/intel/lkp-tests
> 
> Then there are some larger benchmarks we run based on previous regression
> reports and debugs. some of them are:
> 
> YCSB: https://github.com/brianfrankcooper/YCSB
> netperf: https://github.com/HewlettPackard/netperf
> DeathStarBench: https://github.com/delimitrou/DeathStarBench
> HammerDB: https://github.com/TPC-Council/HammerDB.git
> tbench (part of dbench): https://dbench.samba.org/web/download.html
> schbench: https://git.kernel.org/pub/scm/linux/kernel/git/mason/schbench.git
> sched-messaging: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/bench/sched-messaging.c?h=v6.14-rc4
> 
> Some of them are hard to setup the first time; we internally have some
> tools that have made it easy to run these benchmarks in a way that
> stresses the system but we keep an eye out for regression reports to
> understand what benchmarks folks are running in the field.
> 
> Sorry again for the delay and thank you.

Thank you for your support! Wishing you all the best.