I noticed that in the Dockerfile, this is present: --max_old_space_size=192
This causes node.js to crash (out of heap memory) when the processor requires memory to load the necessary "data" for the tests.
I propose that we make this value dynamic so it can be customised.
I have a processor which performs a query at the beginning of a scenario and loads a number of user tokens (JWT) and other records needed for the load test, and with this limit the job gets interrupted when one of the pod reaches that limit. It stopped doing that when I changed 192 to 512.
I noticed that in the Dockerfile, this is present:
--max_old_space_size=192This causes node.js to crash (out of heap memory) when the processor requires memory to load the necessary "data" for the tests.
I propose that we make this value dynamic so it can be customised.
I have a processor which performs a query at the beginning of a scenario and loads a number of user tokens (JWT) and other records needed for the load test, and with this limit the job gets interrupted when one of the pod reaches that limit. It stopped doing that when I changed 192 to 512.
What do you think?