Slide ini digunakan pada webinar yang diselenggarakan oleh CodePolitan atas dukungan Pixel House Studio dengan tema "Memaksimalkan Non-Blocking IO pada Node.js", yang dilaksanakan pada 15 September 2016 pukul 19.00 WIB

1. Memaksimalkan Penggunaan
Non Blocking pada Node.js

2. Rovan Alfarry
CTO of SELabSuite
Informatics Engineering
Institut Teknologi Indonesia
Pixel House Studio
January 2016
Nodejs Programmer
2015-2016

3. Pixel House Studio
Founder: Bramantya Farid in 2010
World Class Product (programming, design, video & internet marketing)

5. 3,4 Million
Keywords
68.000
URLs
300
Projects
 Scraping Google
 Connect to 7 API

6. Why Node.js?
We hate callback hell
We hate single threaded (single point of failure)

7. Blocked by google (use CURL)
20 seconds per-process

8. Google scraping
5 seconds per-process
Selenium

9. Google scraping
2 seconds per-process
PhantomJS

11.  Express js
 Mongodb
 Monk
 Phantom js
 Socket io
 Request
 Nodemon
 PM2
 Redis
 Node
Cluster/NginX/HAProxy
67%
13%
10%
5%
5%
Node.js Python
PHP Java
ElasticSearch
Technologies

12. Non-blocking + node-sync

13.  No standard / No best practice
 Catch everything
 Node.js handles asynchronous I/O requests with a
non-blocking, single-threaded event loop. It is
particularly well-suited to distributed systems that
make a lot of network requests.

15.  Memory Leak
- Heapdump + Chrome Developer Tools
- Force Garbage Collection
node --expose-gc app.js -> global.gc()
 V8 Memory Limit
- node --max-old-space-size=16000 app.js
pm2 start bin/www –node-args=“--max-old-space-
size=16000 ”
V8
Engine

16. EVERY PRO WAS ONCE AN AMATEUR
EVERY EXPERT WAS ONCE A BEGINNER
SO KEEP LEARNING
“

17. Thank You. Any Questions?
Nodejs Indonesia – Telegram Group
We are hiring!
telegram.me/nodejs_jakarta