![Configuration files
{
ports: [0, …, N],
hostname:’xxx.xxx.xxx.xxx’,
transportName: 'http',
concurrentConnection: 20,
}
{
ports: [0, …, N],
hostname: '127.0.0.1',
spawnerName: 'processes',
transportName: http,
disconnect: 2
}
Client Server](https://image.slidesharecdn.com/jsfest2019-191111102208/85/JS-Fest-2019-Autumn-HTTP-TCP-UDP-NodeJS-16-320.jpg)
JS Fest 2019/Autumn. Виталий Кухар. Сравнение кластеризации HTTP, TCP и UDP на процессах и потоках в NodeJS
- 1. Comparing Node.js processes and threads for clustering HTTP, TCP, and UDP Vitalii Kukhar Full Stack Software Engineer at Metarhia 8-9 NOVEMBER ‘19 KIEV, UKRAINEPROFESSIONAL JS CONFERENCE
- 2. Javascript is a single threaded language
- 3. Asynchronous I/O ● Rack: a Ruby Webserver Interface ● NGINX uses an asynchronous, event-driven approach ● an asynchronous event-driven JavaScript runtime ● JavaScript + asynchronous IO + HTTP server stuff
- 4. Performing CPU-intensive operations ● long-running JavaScript functions ● unresponsive page ● limit to perform new asynchronous I / O tasks ● bad user experience
- 5. Inter process communication (IPC) ● child_process module ● cluster module ● net module (tcp client-server) ● BroadcastChannel API, Web Storage API, etc. ● no shared memory
- 6. The worker_threads module ● enables to use threads ● execute JavaScript in parallel ● useful for performing CPU-intensive operations ● shared memory
- 7. Basic Concepts ● process ● thread ● multiprocessing ● multithreading
- 8. What the worker_threads module gave us(before)? ● one process ● one thread ● one event loop ● one JS Engine instance ● one NodeJS instance process thread V8 libuv NodeJS JavaScript
- 9. What the worker_threads module gave us(after)? ● one process ● multiple threads ● one event loop per thread ● one JS Engine Instance per thread ● one NodeJS Instance per thread process thread V8 libuv NodeJS JavaScript thread V8 libuv NodeJS JavaScript
- 10. Tools for working with multithreading
- 11. Server Clusters ● high-availability ● load-balancing ● high performance computing
- 12. Our cluster
- 13. Experimental servers ● http ● tcp ● udp
- 14. Research ● CPU usage ● memory usage ● multiple instances of NodeJS ● worker_threads with I/O-intensive work
- 15. Project structure ● transport ○ http.js ○ tcp.js ○ udp.js ● master.js ● worker.js ● config.js ● spawner ○ processes.js ○ threads.js ● transport ○ http.js ○ tcp.ja ○ udp.js ● master.js ● worker.js ● config.js Client Server
- 16. Configuration files { ports: [0, …, N], hostname:’xxx.xxx.xxx.xxx’, transportName: 'http', concurrentConnection: 20, } { ports: [0, …, N], hostname: '127.0.0.1', spawnerName: 'processes', transportName: http, disconnect: 2 } Client Server
- 17. HTTP Client const requesterAsync = async port => { while (condition) { await requester(port); } };
- 18. TCP Client const requesterAsync = port => { socket.connect({ port, host }, () => socket.write('Run')); socket.on('data', data => { if (condition) { socket.write('Run') } }); };
- 19. UDP Client const requesterAsync = port => { socket.send('Run!', port, host); socket.on('message', (msg, info) => { if (condition) { socket.send('Run', info.port, info.address); } }); };
- 20. Server return { port, workerId || processId, count, memoryUsage }
- 21. Test #1 ● HTTP ● Server ○ 7 processes ○ 7 threads ● Client ○ 70 connections ○ ~3600 rps on port
- 22. HTTP: CPU Usage Processes vs Threads
- 23. HTTP: CPU Usage with disconnects Processes vs Threads
- 24. HTTP: Memory Usage Processes vs Threads
- 25. HTTP: RSS
- 26. Test #2 ● TCP ● Server ○ 7 processes ○ 7 threads ● Client ○ 140 connections ○ ~24000 rps on port
- 27. TCP: CPU Usage Processes vs Threads
- 28. TCP: CPU Usage with disconnects Processes vs Threads
- 29. TCP: Memory Usage Processes vs Threads
- 30. TCP: RSS Processes vs Threads
- 31. Test #3 ● UDP ● Server ○ 7 processes ○ 7 threads ● Client ○ 140 connections ○ ~24000 rps on port
- 32. UDP: CPU Usage Processes vs Threads
- 33. UDP: CPU Usage with stop/restart Processes vs Threads
- 34. UDP: Memory Usage Processes vs Threads
- 35. UDP: RSS Processes vs Threads
- 36. Thank you! Questions? [email protected] 8-9 NOVEMBER ‘19 KIEV, UKRAINEPROFESSIONAL JS CONFERENCE