Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
The Node.js Scalability Myth
Felix Geisendörfer
May 02, 2012
Technology
4
1.3k
The Node.js Scalability Myth
Presentation given on 26.04.2012 at MixIT conference in Lyon, France.
Felix Geisendörfer
May 02, 2012
Tweet
Share
More Decks by Felix Geisendörfer
See All by Felix Geisendörfer
tus.io - Resumable File Uploads (Lightning Talk)
felixge
2
630
Programming flying robots with JavaScript
felixge
2
780
Programming flying robots with JavaScript
felixge
0
400
Programming an AR Drone Firmware with JS (de)
felixge
1
490
Faster than C?
felixge
1
1.1k
Flying robots over a 10.000 mile distance with JavaScript.
felixge
0
360
Faster than C?
felixge
1
430
The power of node.js (with quadcopters)
felixge
0
360
Faster than C?
felixge
0
290
Other Decks in Technology
See All in Technology
Dagu | オンプレ向けワークフローエンジン(WebUI 同梱)
yohamta
0
190
失敗を経験したあなたへ〜建設的なインシデントの振り返りを行うために実践するべきこと〜
nobuakikikuchi
0
190
Unity Package Managerで自作パッケージを配布する方法
yunoda
0
200
TypeScript 4.7と型レベルプログラミング
uhyo
6
3.5k
OSS ことはじめ
hsbt
3
560
Steps toward self-service operations in eureka
fukubaka0825
0
740
Agile and Requirement : アジャイルな要件定義について考える
kawaguti
PRO
9
3.4k
[SRE NEXT 2022]メルカリグループにおけるSREs
srenext
0
300
Stripe Search APIを利用した、LINEとStripeの顧客情報連携/line-dc-202205
stripehideokamoto
0
130
新規ゲームのリリース(開発)前からのSRE活動
tmkoikee
1
370
成長を続ける組織でのSRE戦略:プレモーテムによる信頼性の認識共有 SRE Next 2022
niwatakeru
7
2.7k
LINEスタンプの実例紹介 小さく始める障害検知・対応・振り返りの 改善プラクティス
line_developers
PRO
3
1.7k
Featured
See All Featured
Designing with Data
zakiwarfel
91
3.9k
Debugging Ruby Performance
tmm1
65
10k
Build The Right Thing And Hit Your Dates
maggiecrowley
19
1.1k
KATA
mclloyd
7
8.6k
For a Future-Friendly Web
brad_frost
164
7.4k
BBQ
matthewcrist
74
7.9k
How to name files
jennybc
39
59k
Building Flexible Design Systems
yeseniaperezcruz
310
33k
Support Driven Design
roundedbygravity
86
8.5k
From Idea to $5000 a Month in 5 Months
shpigford
372
44k
The Mythical Team-Month
searls
208
39k
Product Roadmaps are Hard
iamctodd
34
6.1k
Transcript
The Node.js Scalability Myth Felix Geisendörfer 26.04.2012 at MixIT Conference
(Lyon, France)
(@)felixge(.de)
core contributor
transloadit.com (using node since v0.0.6)
History
Ryan Dahl starts the node project (first commit) Feb 16,
2009
Discovered node.js (v0.0.6) ~June, 2009
None
Core Contributor & Module Author node-mysql node-formidable + 30 other
modules
Isaac Schlueter starts the npm package manager (first commit) Sep
29, 2009
Ryan’s talk at JSConf.EU gets people excited about node Nov
7, 2009
(c) @substack Jan 30, 2012 Ryan appoints Isaac to lead
node.js
Topic of this Talk
I need to build an über-scalable web service. It will
be the next big thing!
Easy! I will use node.js and MongoDB!
Easy! I will use node.js and MongoDB!
Because node.js is “scalable”, right?
None
Audience?
Node.js?
Are you measuring app performance in production?
1000 req / s
100 req / s
10 req / s
10 requests / per second = 864000 requests / day
10 req / s
The End?
I REALLY need to build an über-scalable web service!!11!1
Scalability
(c) @substack
The Node.js Scalability Myth • Threads don’t scale • Event
loops do
The Node.js Scalability Myth • Threads don’t scale • Event
loops do (Probably) not true in 2012 (Very likely) not relevant
More relevant • Understanding your tools • Using the right
tool for the job
Node’s Concurrency Model
Node’s Concurrency Model 1 var http = require('http'); 2 3
http.createServer(function(req, res) { 4 res.end('Hello World'); 5 }).listen(8080); server.js
Node’s Concurrency Model $ node server.js
Node’s Concurrency Model • Node loads server.js from disk ->
v8 compiles & executes • listen() allocates and binds a file descriptor • Event Loops starts running
Node’s Concurrency Model 1 while (true) { 2 int r
= select(nfds, readfds, writefds, errorfds, 0); 3 if (r === 0) { 4 continue; 5 } 6 7 // Figure out which fds had activity, accept() on server fds, read() on // connection fds, write() queued writes 8 } Abstracted by libuv Different on Windows
Node’s Concurrency Model • Cooperative multitasking • Low memory usage
• Fast / efficient • Simple (compared to threads)
Vertical Scalability
Adding more resources to a single node
Vertical Scalability • CPU • GPUs • Memory • Disk
• Network
CPU
CPU (v8) • V8 compiles JS to Assembly • Just-in-time
compilation (JIT) • Does pretty well in those language benchmarks
Computers of the future will have hundreds of cores!
CPU • Node is single threaded (runs on a single
CPU) • No shared memory
But ...
Does your problem require shared memory?
If yes: Don’t use node
And: Good Luck
If no: child_process.fork()
Redis / ZeroMQ are your friends
GPUs
GPUs • No support in node itself • node-cuda addon
by Kashif Rasul
Memory
Memory • No hard memory limit on 64 bit (since
node-0.6 / v8-3.7) • JS is a garbage collected language (avoid huge heaps) • Buffers do not count towards heap
Network
Network • Node’s concurrency model is optimized for networking •
Good at fully saturating available network resources
Disk
Disk • Done in thread pool • Unfortunately along with
DNS at this point • Throughput ok, but not ideal yet • sendfile() not working yet
Does node scale vertically?
Yeah, good enough
Horizontal Scalability
Adding more nodes to a system
Bad News
Node.js has no horizontal scaling features
Even worse
This s#@t is really hard
Problems • De-coupling / encapsulation • CAP Theorem • System
Automation
...
Good Luck
One tip
Monitor & Measure! • Collect: node-measured, statsd, ... • Analyze:
Graphite, Librato Metrics, ... • Debug
So if node doesn’t have magic scaling, what is it
good for?
<Live Coding>
tl;dr • Know your requirements • There are no silver
bullets
Questions? Slides will be available at felixge.de
Thanks
Feedback