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
If I use in one execution -w and -r and the --timelimit, then the timelimit duration is for the total execution and not for each case (write and read). Could be considered such option if it does not exist already?
regards,
George
The text was updated successfully, but these errors were encountered:
Just to make sure I understand the request correctly: You are suggesting that when a time limit of (for example) 60 seconds is exceeded in the write phase, then the read phase should still run and use again a timit limit of 60 seconds, correct?
So far my assumption was that you could just run two separate commands, one for the write phase and one for the read phase, each with a time limit. That's why I did not add such an option in the past. However, it would be relatively easy to add such an option if it is helpful for you.
Yes, this is correct about the example. You could name it different for full compatibility with the behavior until now, if it is an issue. You are right, about the two commands but makes it more easy to use one command.
Hi George, ok, I will add this for you. It will take a few weeks because I'm currently trying to finalize the new S3 support for elbencho. Will let you know here when it's available.
Hi,
If I use in one execution -w and -r and the --timelimit, then the timelimit duration is for the total execution and not for each case (write and read). Could be considered such option if it does not exist already?
regards,
George
The text was updated successfully, but these errors were encountered: