node-clinic VS autocannon

It's basic, but it works. You can see what function or 3rd library is after your resources and debug them locally (For example, by using ClinicJS - https://clinicjs.org/)

Clinic.js

Clinic.js - performance analysis tooling.

I’ve also seen some pretty bad event loop saturation causing significant delays. Run this https://clinicjs.org

Clinic.js includes three tools to help diagnose and pinpoint performance issues in Node.js applications. It’s surprisingly easy to use. All you need to do is install the module from npm and run it. This will generate reports for you that make troubleshooting much easier.

To compare the two servers, we used two packages. The first one was ClinicJS, an open-source set of tools used to diagnose NodeJS performance issues, which also gives you suggestions and points you in a direction to fix the diagnosed problems. The second one was hey, a CLI tool to send some load to the server. Below we show how we use them and the results of these comparisons.

WTF? 1.15 GB of RAM while idle, have you tried to profile the app? maybe you have some memory leaks, use node clinic to diagnose performance issues.

You can use https://clinicjs.org along with autocannon to identify bottleneck

Autocannon GitHub Repository

To make things interesting, let’s send some requests to this server with autocannon:

Using autocannon, I did the following script to simulate 500 concurrent connections over 30 seconds:

We then used autocannon to measure the throughput (requests per second) of each runtime server-rendering our React app.

You could also use tools like autocannon to see how many requests/second you can achieve with various methods. : https://github.com/mcollina/autocannon

I used autocannon to test the function at 100 concurrent executions for 30 seconds. I also used Lambda Power Tuning to find the ideal memory configuration, which proved to be 512MB. All the results are available.

Moreover, if your blocking issue is appearing only on heavy load, you can easily test it using the very nice --autocannon CLI param (see it with clinic flame --help) where you can specificy autocannon options to generate some HTTP load on your web service.

I packaged them both with Docker and deployed them to an EC2 instance, each behind an Nginx reverse proxy I setup in docker-compose. I'm currently testing performance using autocannon from my laptop like this: `autocannon -a 5000 -w 10 URL` (5000 requests with 10 workers), and both apps complete in around 40 seconds. The EC2 instance is in Oregon and I'm testing from Toronto.

You can test it by yourself using console.time(). You can use autocannon to stress-test your http server to see what is really the best options.

When I test this with autocannon making three simultaneous requests (autocannon --connections 3 --amount 3 --timeout 10000 --no-progress http://localhost:5678/):