RangeError

[jchannon]

Hi I'm a noob to load testing but I copied the sample Hello World from the node home page and fired up the server then ran node loadtest --rps 2000 http://localhost:1337 (I didnt install globally).

I got the result:

[Sun Feb 02 2014 12:10:19 GMT+0000 (GMT)] INFO Requests: 0, requests per second: 0, mean latency: 0 ms
[Sun Feb 02 2014 12:10:24 GMT+0000 (GMT)] INFO Requests: 9170, requests per second: 1834, mean latency: 30 ms
[Sun Feb 02 2014 12:10:24 GMT+0000 (GMT)] INFO Errors: 1, accumulated errors: 1, 0% of total requests
[Sun Feb 02 2014 12:10:36 GMT+0000 (GMT)] INFO Requests: 18304, requests per second: 759, mean latency: 520 ms
[Sun Feb 02 2014 12:10:36 GMT+0000 (GMT)] INFO Errors: 1945, accumulated errors: 1946, 10.6% of total requests
[Sun Feb 02 2014 12:10:36 GMT+0000 (GMT)] INFO Requests: 18304, requests per second: 0, mean latency: 0 ms
[Sun Feb 02 2014 12:10:36 GMT+0000 (GMT)] INFO Errors: 0, accumulated errors: 1946, 10.6% of total requests

net.js:0
(null)

RangeError: Maximum call stack size exceeded

Is it supposed to error like that? It also killed the Hello World server..

Server running at http://127.0.0.1:1337/
Assertion failed: (fd > -1), function uv__close, file ../deps/uv/src/unix/core.c, line 413.
Abort trap: 6

[alexfernandez]

Hi,

I cannot reproduce your issue: I run bin/loadtest.js from the package root against the node.js sample server and got this:

 $ node bin/loadtest.js --rps 2000 http://localhost:1337
[Mon Feb 03 2014 00:59:17 GMT+0100 (CET)] INFO Requests: 0, requests per second: 0, mean latency: 0 ms
[Mon Feb 03 2014 00:59:22 GMT+0100 (CET)] INFO Requests: 9859, requests per second: 1972, mean latency: 0 ms
[Mon Feb 03 2014 00:59:27 GMT+0100 (CET)] INFO Requests: 19891, requests per second: 2006, mean latency: 0 ms
[Mon Feb 03 2014 00:59:32 GMT+0100 (CET)] INFO Requests: 29775, requests per second: 1972, mean latency: 0 ms

and so on. Same thing if I install globally and run with loadtest --rps 2000 http://localhost:1337. It runs beautifully!

A few questions:

• What operating system are you on?
• What version of loadtest in package.json?
• What command are you exactly running, node bin/loadtest.js ...?

Please send any other info you think can help pinpoint the issue. Thanks!

[jchannon]

I'm on OS X Mavericks
Version 0.2.8
I change directory to bin then call node loadtest --rps 2000 http://localhost:1337

[alexfernandez]

I finally got to reproduce this issue on a Mac OS X Maverick, it behaves exactly as you report. It is not supposed to fail like that, but then, at that point the system is so thoroughly overloaded that it does not answer for a while. The reason for --rps is to find the point at which the server still answers in time, and this is clearly beyond that point.

Still, worth taking a look. I will leave this issue open.

[alexfernandez]

On second thought, range errors are quite hard to pinpoint and the value in doing it is not clear to me. I am closing, please reopen if it is still an issue for you.