Add ramp-up option for K6 job #126
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/xk6-frostfs#126
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Performance tools quite often has ramp-up option to stabilize test results (period of time when load being generated to the target system but the tool does not acount this period of time in statistics).
I do suggest to add ramp-up option in K6 implementation. Something like:
where ramp_time: 600 means after wiping data and generation of preset run ramp-up period for 600 seconds.
actual test starts after ramp period.
The sentence looks unfinished.
Sentence finishied.
I assume it's not the right place for this issue. It can be implemented within 1d in the testlib repo.
Load config and actual k6 usage are implemented in frostfs-testlib repo
load_config.py
background_load_controller.py