Sergii Onufriienko sonufrienko

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

Kafka Topics

List existing topics

bin/kafka-topics.sh --zookeeper localhost:2181 --list

Describe a topic

bin/kafka-topics.sh --zookeeper localhost:2181 --describe --topic mytopic

Purge a topic

bin/kafka-topics.sh --zookeeper localhost:2181 --alter --topic mytopic --config retention.ms=1000

... wait a minute ...

The Problem

Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)

One possibly-right way:

Add a port forwarding rule via iptables.

First, I listed the rules currently running on the NAT (Network Address Translation) table:

Create Certificates

git clone https://github.com/OpenVPN/easy-rsa
cd easy-rsa/easyrsa3
./easyrsa init-pki
./easyrsa build-ca nopass
./easyrsa build-server-full server nopass
./easyrsa build-client-full client1.domain.tld nopass

	const promisify = f => (...args) =>
	new Promise((resolve, reject) => {
	f(...args, (err, res) => {
	if(err) {
	return reject(err);
	}
	return resolve(res);
	});
	});

	# Generate private and public keys
	# RSA 2048
	# Quiet mode
	# Without a passphrase
	ssh-keygen -t rsa -b 2048 -q -N '' -m PEM -f private.key \
	&& rm private.key.pub \
	&& openssl rsa -in private.key -pubout -outform PEM -out public.key

	# Get all Rules from Listener
	aws elbv2 describe-rules \
	--listener-arn {alb-listener-arn}

	# Get Rule
	aws elbv2 describe-rules \
	--rule-arn {alb-rule-arn}

	# Modify Rule
	aws elbv2 modify-rule \

	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

	# count and group ports
	netstat -ant \| awk '{print $6}' \| sort \| uniq -c \| sort -n