<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Performance on Dev Toolkit</title><link>https://wen.yunshangtool.cn/tags/performance/</link><description>Recent content in Performance on Dev Toolkit</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wen.yunshangtool.cn/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Node.js Performance Optimization Techniques</title><link>https://wen.yunshangtool.cn/posts/nodejs-performance/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://wen.yunshangtool.cn/posts/nodejs-performance/</guid><description>Node.js handles thousands of concurrent connections efficiently, but poor code can still cause performance bottlenecks.
Event Loop Blocking: CPU-intensive operations block the event loop. Offload heavy computation to worker threads or child processes.
Memory Leaks: Common sources include global variables, forgotten timers, and closures holding references. Use --inspect for heap snapshots.
Database Optimization: Use connection pooling, index frequently queried fields, avoid N+1 queries, and use caching (Redis) for hot data.</description></item></channel></rss>