Do not use generator in reader VU #118

New issue

Open

opened 2024-01-12 14:05:55 +00:00 by fyrchik · 1 comment

fyrchik commented

2024-01-12 14:05:55 +00:00

Owner

Even after #117 we still have a problem: generator is created in every thread.
We can share it between threads (albeit with a possible loss in perfomance -- now the returned slice must be copied, so the problem is not solved)

The problem is that there is no per-VU init stage, but maybe we can find some kludge.

Even after #117 we still have a problem: generator is created in every thread. We can share it between threads (albeit with a possible loss in perfomance -- now the returned slice must be copied, so the problem is not solved) The problem is that there is no per-VU init stage, but maybe we can find some kludge.

fyrchik added the

bug

label 2024-01-12 14:06:12 +00:00

fyrchik commented

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

Author

Owner

Because we do not have per-VU init stage, I see 2 options:

Create generator on the first usage in each thread. Could skew results for short tests.
Create an array of generators in setup and use VU id so that each VU uses its own.

Because we do not have per-VU init stage, I see 2 options: 1. Create generator on the first usage in each thread. Could skew results for short tests. 2. Create an array of generators in `setup` and use VU id so that each VU uses its own.