Is there any limit for HTTP calls

Hi,

I have a simlutation which is making HTTP calls to Node Server.

constantUsersPerSec(50) during(60 minutes)

Now after 5 minutes my gatling shows me error as connection timedout. When I check the nodejs server logs, I dont see any new connection logs. Gatling is hosted on AWS EC2 t2-mdeium and node is hostedo nAWS t2-large.

The initial calls are made, but after 5 minutes almost 90% calls are timedout. I checked both the server load, and it was in good shape.

Is there any limitation from gatling or from AWS ec2 instance? Did anyone face this issue before?

Most likely, the problem looks to be on the client side machine.

Check your client machine’s ulimit settings and monitor the number of open FDs for your gatling process for the duration of the run.

Hi,

I am not good at process, but based on your reply this is the server stat when the load testing is being performed:

`
NODE:
cat /proc/14525/limits
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 7861 7861 processes
Max open files 4096 4096 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 7861 7861 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us

cat /proc/14819/limits
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 7861 7861 processes
Max open files 4096 4096 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 7861 7861 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
`

NodeJS is running on cluster mode, so 2 process are spawned.

The FDs on node server for each process is above 600

Gatling server stats:

`
GATLING
cat /proc/26520/limits
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 31537 31537 processes
Max open files 4096 4096 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 31537 31537 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us

`

The FDs are around 200.

What does the above stats mean? Is the server is having problem?

Hi Nirja,

The load would exceed 4000 connections after just 13 seconds with the way you inject the load. Which is higher than the open file limit on your Gatling server.

`
constantUsersPerSec(50) during(60 minutes)

`

You might wanna check this doc and adjust the Gatling servers.