<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Asynchronous-Io on Scholion</title><link>https://scholion.thluiz.com/tags/asynchronous-io/</link><description>Recent content in Asynchronous-Io on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Fri, 24 Apr 2015 08:40:20 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/asynchronous-io/index.xml" rel="self" type="application/rss+xml"/><item><title>On problems with threads in node.js</title><link>https://scholion.thluiz.com/notes/on-problems-with-threads-in-node-js/</link><pubDate>Fri, 24 Apr 2015 08:40:20 -0300</pubDate><guid>https://scholion.thluiz.com/notes/on-problems-with-threads-in-node-js/</guid><description>The article shows how Node.js relies on libuv’s thread pool for asynchronous work, why the default pool size can limit parallelism, and how that can block other tasks.</description></item></channel></rss>