TrueCloudLab/xk6-frostfs

Allow to specify sizes with units #111

New issue

Open

opened 2023-12-15 10:07:02 +00:00 by fyrchik · 2 comments

fyrchik commented

2023-12-15 10:07:02 +00:00

Owner

We have WRITE_OBJ_SIZE which is in bytes and now also #110 which is in gigabytes.
It can be confusing, and could be better if we did WRITE_OBJ_SIZE=100k. The default would be bytes.

We have `WRITE_OBJ_SIZE` which is in bytes and now also https://git.frostfs.info/TrueCloudLab/xk6-frostfs/pulls/110 which is in gigabytes. It can be confusing, and could be better if we did `WRITE_OBJ_SIZE=100k`. The default would be bytes.

fyrchik referenced this issue

2023-12-15 10:08:44 +00:00

Allow to limit engine size for local scenarios #110

dstepanov-yadro commented

2023-12-15 10:34:46 +00:00

Member

WRITE_OBJ_SIZE in KB.

`WRITE_OBJ_SIZE` in KB.

dstepanov-yadro referenced this issue

2023-12-15 11:08:12 +00:00

Allow to limit engine size for local scenarios #110

fyrchik added the

labels 2024-01-11 17:32:17 +00:00

fyrchik commented

2024-12-19 12:47:43 +00:00

Author

Owner

@dstepanov-yadro now you see, I am confused.
Then the default would be kb, to be backwards compatible.

@dstepanov-yadro now you see, I am confused. Then the default would be kb, to be backwards compatible.

Sign in to join this conversation.

No labels

good first issue

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/xk6-frostfs#111

No description provided.