Skip to content

Conversation

@xemul
Copy link
Contributor

@xemul xemul commented Dec 3, 2025

Add a test that populates run-queue and measures the time it takes for the scheduler to process one.
Useful to measure the effect the runqueue implementation has.

@xemul
Copy link
Contributor Author

xemul commented Dec 4, 2025

upd:

  • shuffle the tasks (once -- upon creation) for this test

Add the `--parameter name=value` vector option. Tests may then do
`perf_tests::get_parameter("foo")` to get the user-configured parameter
and update themselves accordingly.

It will be useful for future scanning tests, as they show very different
results on collections of different sizes, and hard-coding a test for
each interesting collection size is too much code.

Signed-off-by: Pavel Emelyanov <xemul@scylladb.com>
Add a test that populates run-queue with the given number of tasks (100 by
default) and measures the time it takes for the scheduler to process one.

No allocations/frees happen measure-time, tasks are pre-populated.

Signed-off-by: Pavel Emelyanov <xemul@scylladb.com>
@xemul xemul force-pushed the br-perf-test-runqueue-cont branch from 53240d4 to bf9f5b9 Compare December 11, 2025 11:43
@xemul
Copy link
Contributor Author

xemul commented Dec 11, 2025

upd:

@xemul xemul requested a review from avikivity December 11, 2025 12:07
@xemul
Copy link
Contributor Author

xemul commented Dec 18, 2025

@avikivity , please review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant