chore: element ratio parameter for seeder #3844
Conversation
Signed-off-by: Vladislav Oleshko <[email protected]>
|
|
||
| keys = await async_client.keys() | ||
| assert (await async_client.llen(keys[0])) == 1 | ||
| assert len(await async_client.lpop(keys[0])) == 10_000 |
There was a problem hiding this comment.
A question:
if element_size_ratio=1/2 then data_size is 10k ** (1/2) == 100 and variance is 1. So dsize=100. My question is, why do we xor the dsize ? That is: LG_funcs.esize = math.ceil(dsize ^ delement_ratio) which is how many elements a given type should contain (that is llen(keys[0])).
So to sumamrize:
- Why do we
xorthis ?LG_funcs.esize = math.ceil(dsize ^ delement_ratio) - Why do we express the number of elements per set via all of this? Can't we just be specific on how many elements we want of a given size each ?
There is something I am missing so I am asking here 😄
There was a problem hiding this comment.
- It's not xor, it's power 🙃
- If it's too difficult and fragile, no one will use it properly. It's just a 0/1 slider: 0 means smallest possible elements, 1 means biggest possible
There was a problem hiding this comment.
For 1. power is ** not caret ^ which is xor ?
There was a problem hiding this comment.
There was a problem hiding this comment.
I brainfarted. It's LUA not python 😮💨 🤦
Now it all makes sense. Ignore my blindness....
There was a problem hiding this comment.
Lol @dranikpg we make the comment at exact same time. I did not read your link but somehow I noticed and then you replied at the exact same moment I figured and reply 🤣
Fixes #3840
Added element_size_ratio parameter to both static and dynamic seeder
data size ~ data volume, element size = data size ^ ratio, element count = data volume / element size