Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve reading VUs to work with objects produced by writing VUs #20

Open
vdomnich-yadro opened this issue Sep 22, 2022 · 0 comments
Open
Labels
I4 No visible changes performance More of something per second S3 Minimally significant U4 Nothing urgent

Comments

@vdomnich-yadro
Copy link
Contributor

Currently reading VUs are reading a fixed set of objects that were pre-generated before K6 run. As result, readers are sending requests that are covering very narrow set of data in neoFS. More realistic scenario would be if reading VUs attempted to read the objects that have been created by writing VUs within the same load session.

We can achieve this by storing objects in registry (in writing functions) and then picking them up with ObjSelector in reading VUs.

@roman-khimov roman-khimov added S3 Minimally significant I4 No visible changes performance More of something per second labels Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I4 No visible changes performance More of something per second S3 Minimally significant U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

3 participants