Use SelectorAwaiting in case of read and delete load in s3_dar.js scenario #150
1 changed files with 1 additions and 1 deletions
|
@ -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_exit_on_null = undefined;
|
||||
|
||||
if (registry_enabled && delete_age) {
|
||||
if (registry_enabled ) {
|
||||
|
||||
obj_to_delete_exit_on_null = (write_vu_count == 0) && (read_vu_count == 0)
|
||||
|
||||
let constructor = obj_to_delete_exit_on_null ? registry.getOneshotSelector
|
||||
|
|
Loading…
Reference in a new issue
How does it help?
In case we are running both read and delete load we don't use SelectorOneshot, but use SelectorAwaiting