Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Memory issue for longer tests

See original GitHub issue

We are seeing an issue with artillery running out of memory for longer tests - memory gradually increases until it hits limit, then CPU spikes and the test crashes. I don’t know if there is a memory leak somewhere - we are running tests up to around 30 requests per second. Artillery is running in a docker container (with 1GB of memory allocated) on a t2.small in AWS.

Config has multiple phases:

  phases:
    - duration: 300
      arrivalRate: 10
    - duration: 300
      arrivalRate: 12
    - duration: 300
      arrivalRate: 14
    - duration: 300
      arrivalRate: 16
    - duration: 300
      arrivalRate: 18
    - duration: 300
      arrivalRate: 20
    - duration: 300
      arrivalRate: 22
    - duration: 300
      arrivalRate: 24
    - duration: 300
      arrivalRate: 26
    - duration: 300
      arrivalRate: 28
    - duration: 300
      arrivalRate: 30

with each scenario just calling a single GET request

Issue Analytics

State:
Created 7 years ago
Comments:23 (14 by maintainers)

Top GitHub Comments

1reaction

dteirneycommented, Dec 6, 2016

@hassy you can see the YAML configuration for one of the problematic artillery scripts at https://github.com/orionhealth/apigee-edgemicro-testing/blob/master/templates/artillery/stream-test.yaml

I’m using Node 7.2.0 and artillery 1.5.0-17. Artillery fails with a memory allocation error. I’ve had to bump up the heap size for V8 to get some scripts to run without exploding using:

node --max_old_space_size=3072 `which artillery` run -e edgemicro stream-test.yaml

I’m pretty sure that covers answers to questions 1 through 4. The sizes of the response are obvious from the requests in the configuration.

0reactions

benlippcommented, May 24, 2017

An Artillery test script that would reliably reproduce the problem would be ideal.

https://gist.github.com/benlipp/7ca805a4f3dfe4e3bbe2b392332ef213

Maybe you need to run Node.js with an increased memory limit to be able to run your tests, it’s impossible to say without knowing what your tests are doing.

How would I do this? Running on Ubuntu 16.04

Are you able to run the same tests on an earlier version of Artillery without seeing the same problem?

I’m not sure, I haven’t tried an earlier version. How would I do that?

Top Results From Across the Web

Extended Memory Testing - N-able

Extended memory testing stress tests the RAM for errors by writing patterns of ones and zeroes to unused parts of RAM. It reads...

Cramming may help for next-day exams. But for long-term ...

Cramming may help for next-day exams. But for long-term memory, spacing out study is what works. By Sanjay Sarma. and. Luke Yoquinto.

Free Memory Test (5 Mins) – Short Term and Long Term

In Cognitive Psychology, long term memory is classified as information stored and retrieved for longer than a few minutes. In this memory test, ......

Should You Take an Online Memory Loss Test? - HumanGood

If you're worried about memory loss, your doctor should be the first stop. A simple test may not tell you what you need...

[Self-Test] Do You Have a Working Memory Deficit? - ADDitude

If you have concerns about possible working memory problems, ... you like to receive your working memory symptom test results — plus more...