TrueCloudLab/xk6-frostfs
39
0
Fork 19
Code Issues 35 Pull requests Releases Activity Actions

Use SelectorAwaiting in case of read and delete load in s3_dar.js scenario #150

Merged
fyrchik merged 1 commit from mmalygina/xk6-frostfs:investigate-deletes into master 2024-09-04 19:51:18 +00:00
Conversation 1 Commits 1 Files changed 1 +1 -1
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
scenarios/s3_dar.js
View file

@ -86,7 +86,7 @@ const delete_age = __ENV.DELETE_AGE ? parseInt(__ENV.DELETE_AGE) : undefined;
let obj_to_delete_selector = undefined; let obj_to_delete_selector = undefined;
let obj_to_delete_exit_on_null = undefined; let obj_to_delete_exit_on_null = undefined;
if (registry_enabled && delete_age) { if (registry_enabled ) {
fyrchik commented 2024-06-20 16:35:06 +00:00
Outdated
Review
Copy link

How does it help?

How does it help?
mmalygina commented 2024-06-21 07:42:23 +00:00
Outdated
Review
Copy link

In case we are running both read and delete load we don't use SelectorOneshot, but use SelectorAwaiting

In case we are running both read and delete load we don't use SelectorOneshot, but use SelectorAwaiting
obj_to_delete_exit_on_null = (write_vu_count == 0) && (read_vu_count == 0) obj_to_delete_exit_on_null = (write_vu_count == 0) && (read_vu_count == 0)
let constructor = obj_to_delete_exit_on_null ? registry.getOneshotSelector let constructor = obj_to_delete_exit_on_null ? registry.getOneshotSelector