<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance-Tuning on Scholion</title><link>https://scholion.thluiz.com/tags/performance-tuning/</link><description>Recent content in Performance-Tuning on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Tue, 06 Oct 2026 04:20:06 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/performance-tuning/index.xml" rel="self" type="application/rss+xml"/><item><title>600k concurrent websocket connections on AWS using Node.js</title><link>https://scholion.thluiz.com/notes/600k-concurrent-websocket-connections-on-aws-using-node-js/</link><pubDate>Thu, 16 Apr 2015 15:30:24 -0300</pubDate><guid>https://scholion.thluiz.com/notes/600k-concurrent-websocket-connections-on-aws-using-node-js/</guid><description>The post explains how to push an AWS EC2 instance toward 600k persistent websocket connections by choosing Node.js, using ws and sticky-session, and raising V8 and system limits.</description></item></channel></rss>