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
Is your feature request related to a problem? Please describe.
We have workloads that consist of many small jobs (see https://github.com/redhat-performance/web-burner/blob/main/workload/cfg_icni2_node_density2.yml for an example). Instead of defining the property waitWhenFinished per job, it would be great to be able to define it globally for a whole kube-burner run.
By defining the property per job as it is today, we introduce a long wait between jobs that not reflects the workload we are trying to mimic.
Describe the solution you'd like
To be able to define the property waitWhenFinished globally for a whole kube-burner run. That way one job would run after another.
Describe alternatives you've considered
If we set waitWhenFinished: false unfortunately we do not get the pod creation latency times, that are one of the most important KPIs for our use cases.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We have workloads that consist of many small jobs (see https://github.com/redhat-performance/web-burner/blob/main/workload/cfg_icni2_node_density2.yml for an example). Instead of defining the property
waitWhenFinished
per job, it would be great to be able to define it globally for a whole kube-burner run.By defining the property per job as it is today, we introduce a long wait between jobs that not reflects the workload we are trying to mimic.
Describe the solution you'd like
To be able to define the property
waitWhenFinished
globally for a whole kube-burner run. That way one job would run after another.Describe alternatives you've considered
If we set
waitWhenFinished: false
unfortunately we do not get the pod creation latency times, that are one of the most important KPIs for our use cases.The text was updated successfully, but these errors were encountered: