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
Currently there are: realistic and striped.
I have the idea about: experimental.
The results should not be visible by default in the normal results page of a round. Maybe even to have separate runs for this test implementations - to improve the feedback speed. Maybe limit the total number per framework to stay around 24 hours wall clock duration.
In general it should help the project participants to play and experiment with tuning the "knobs": how many threads to spawn, how many connections to the database, how many requests to queue.
Currently this is very hard if you don't have similar hardware to play with and the time-span is huge.
The text was updated successfully, but these errors were encountered:
Currently there are: realistic and striped.
I have the idea about: experimental.
The results should not be visible by default in the normal results page of a round. Maybe even to have separate runs for this test implementations - to improve the feedback speed. Maybe limit the total number per framework to stay around 24 hours wall clock duration.
In general it should help the project participants to play and experiment with tuning the "knobs": how many threads to spawn, how many connections to the database, how many requests to queue.
Currently this is very hard if you don't have similar hardware to play with and the time-span is huge.
The text was updated successfully, but these errors were encountered: