GitHub - felixge/faster-than-c: Talk outline: Faster than C? Parsing binary data in JavaScript.
Hi everybody, my name is Felix Geisendörfer and today I'd like to talk about "Faster than C? Parsing Node.js Streams!". Before I get started, I would like to appologize for the "Title Bait". This talk is analyzing the performance of JavaScript vs C-Bindings for MySQL in node.js, but not JavaScript vs. C itself. So, I have this module I wrote that lets you talk to MySQL databases in node.js. I star
node.jsã®ãƒ‘フォーマンスを調ã¹ã¦ã¿ãŸ
ã“ã‚“ã°ã‚“ã¯ã€‚ å··ã§ã¯ã€Œnode.jsã¯è»½é‡ã‹ã¤é«˜é€Ÿã よーã€ã¨å™‚ã•ã‚Œã¦ã‚‹ã«ã‚‚ã‹ã‹ã‚らãšã€è‰²ã€…探ã—ã¦ã‚‚ã€ã©ã‚Œã»ã©è»½é‡ã§ã©ã‚Œã»ã©é«˜é€Ÿãªã®ã‹ã‚’検証ã—ã¦ã„ã‚‹ã¨ã“ã‚ãŒæ—¥æœ¬èªžã§ã¯ã‚ã¾ã‚Šè¦‹ã¤ã‹ã‚Šã¾ã›ã‚“。 ãã®ç‚ºã€ä»Šå›žã¯ã€WebSocketを用ã„ãŸsocket.ioã®é€Ÿåº¦/メモリ使用é‡èª¿æŸ»ã‚’ã—ã¦ã¿ã¾ã—ãŸã€‚ã¾ãŸã€msgpack-rpc改変版をWebSocketã®ä¸Šã«å®Ÿè£…ã—ãŸãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨æ¯”較もã—ã¦ã¿ã¾ã—ãŸã€‚ テストã¯ä»¥ä¸‹ã§ã™ãŒã€æ¬¡ã®æ³¨æ„点をè¸ã¾ãˆã¦ãŠè©¦ã—ãã ã•ã„。 デモã¯ã€ã©ã¡ã‚‰ã‚‚ã•ãらã®VPS 512ã€CentOS 5.7, kernel 2.6.18-274.18.1.el5 x86_64上ã«æ§‹ç¯‰ã—ã¦ã‚ã‚Šã¾ã™ã€‚ node.jsã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã€v0.6.12。socket.ioã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¯ã€0.9.1-1を利用ã—ã¦ã„ã¾ã™ã®ã§ã€æœ€æ–°ç‰ˆã¯ã‚ˆã‚Šè‰¯ã„パフォーマンスãŒå‡ºã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。 socket-io版ã¯ã€ãƒ‡ãƒ¢
Node.js scalability testing with EC2
The sprites project leverages Node.js to implement it’s server logic. The server is surprisingly simple JavaScript code which accepts long-poll COMET HTTP connections from it’s C++ clients in order to push JSON format sprite information in real-time. Sprites can be thrown from one client’s desktop to another via HTTP. The server maintains a network topology (which is worth a separate post in itsel
Scaling node.js to 100k concurrent connections!
UPDATE: Broke the 250k barrier, too :] The node.js powered sprites fun continues, with a new milestone: That’s right, 100,004 active connections! Note the low %CPU and %MEM numbers in the picture. To be fair, the CPU usage does wander between about 5% and 40% – but it’s also not a very beefy box. This is on a $0.12/hr rackspace 2GB cloud server. Each connection simulates sending a single sprite ev
SockJS benchmark | Eat at Joe's
Introduction After I implemented sockjs-tornado backend, I decided to benchmark it. Luckily, there was good socket.io performance test out there and I was able to use their test application to benchmark SockJS server performance. This test will only cover raw messaging performance over Websocket connection(s) for different server implementations of the SockJS protocol. It won't test any streaming
Node.js Performance Case Study
This document compares performance of Node.js, Apache + PHP, Manhattan, and Mojito frameworks. Node.js showed superior performance scaling to over 3,000 requests per second with low latency. Manhattan and Mojito also outperformed Apache + PHP in some tests. The document concludes Node.js is well-suited for I/O bound use cases that require handling many concurrent requests quickly and reliably.Read
ãƒãƒŠãƒŠã§ãƒãƒ³:node.js：åŒæ™‚接続ã—ã¦ã‚‹ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚’増やã—続ã‘ã¦ã¿ãŸã¨ãã®ãƒ¡ãƒ¢
2011å¹´10月08æ—¥ node.js：åŒæ™‚接続ã—ã¦ã‚‹ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚’増やã—続ã‘ã¦ã¿ãŸã¨ãã®ãƒ¡ãƒ¢ node.jsã«æŽ¥ç¶šã—ã£ã±ãªã—ãªã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚’増やã™ã¨ã©ã†ãªã‚‹ã‹ãƒ†ã‚¹ãƒˆã—ã¦ã¿ãŸã€‚ 知りãŸã‹ã£ãŸã®ã¯ãƒ¡ãƒ¢ãƒªã‚„CPUã®ä½¿ç”¨é‡ãŒã©ã†ãªã‚‹ã‹ã€æŽ¥ç¶šä»¶æ•°ã¯ã„ã‹ã»ã©ã¾ã§okã‹ã€ã¨ã„ã£ãŸã“ã¨ã€‚ 接続数をã©ã‚„ã£ã¦å¢—ã‚„ã™ã‹ã«ã¤ã„ã¦ã¯ã„ã„案ãŒæµ®ã‹ã°ãªã‹ã£ãŸã®ã§ã€ãƒœã‚¿ãƒ³ã‚’押ã™ã¨çª“ãŒä½•å€‹ã‚‚é–‹ãブラクラを用æ„ã—ãŸã€‚ 窓を複数個ã„ã£ãºã‚“ã«é–‹ãボタンã®ä»–ã«ã€æŽ¥ç¶šä»¶æ•°ã‚’å•ã„åˆã‚ã›ã‚‹ãƒœã‚¿ãƒ³ã‚‚付ã‘ã‚‹ã“ã¨ã§æŽ¥ç¶šæ•°ã‚’ã¡ã‚‡ãã¡ã‚‡ã確èªã—ãªãŒã‚‰çª“ã‚’ã°ã‚“ã°ã‚“é–‹ã„ã¦ã¿ã‚‹ã“ã¨ã«ã€‚ node.jsã®åŒæ™‚接続数上é™ã¯ãƒ•ã‚¡ã‚¤ãƒ«ãƒ‡ã‚£ã‚¹ã‚¯ãƒªãƒ—ã‚¿ã®ä¸Šé™æ•°ã«å·¦å³ã•ã‚Œã‚‹ ã¨ã„ã†ã®ãŒçŸ¥ã‚ŒãŸã“ã¨ã€‚ æ¥ãšã‹ã—ãªãŒã‚‰ãƒ•ã‚¡ã‚¤ãƒ«ãƒ‡ã‚£ã‚¹ã‚¯ãƒªãƒ—ã‚¿ãªã‚‹ã‚‚ã®ã‚‚知らãªã‹ã£ãŸã®ã§ã€ãれを知れãŸã®ã‚‚プラスã‹ã€‚ 以下ã€ãƒ†ã‚¹ãƒˆã®æ™‚ã®ãŠã¼ãˆæ›¸ã。 サーãƒã¯ã•ãらã®VPSã§ã€512
Blazing fast node.js: 10 performance tips from LinkedIn Mobile
Blazing fast node.js: 10 performance tips from LinkedIn Mobile In a previous post, we discussed how we test LinkedIn's mobile stack, including our Node.js mobile server. Today, we’ll tell you how we make this mobile server fast. Here are our top 10 performance takeaways for working with Node.js: 1. Avoid synchronous code By design, Node.js is single threaded. To allow a single thread to handle man
Registration: Machine learning & data conference | O'Reilly Strata
We’ve made the very difficult decision to cancel all future O’Reilly in-person conferences. Instead, we’ll continue to invest in and grow O’Reilly online learning, supporting the 5,000 companies and 2.5 million people who count on our experts to help them stay ahead in all facets of business and technology. Come join them and learn what they already know. Become an O’Reilly online learning member
Digging Deeper with htracr
Hi, I’m Mark Nottingham. I write about the Web, protocol design, HTTP, Internet governance, and more. This is a personal blog, it does not represent anyone else. Find out more. Comments? Let's talk on Mastodon. @mnot@techpolicy.social other HTTP posts Yet More New HTTP Specs Wednesday, 8 June 2022 A New Definition of HTTP Monday, 6 June 2022 How Multiplexing Changes Your HTTP APIs Sunday, 13 Octob
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Node.js Application Performance Monitoring | Node.js Monitoring Tools
Good night, Posterous
{{#tags}}- {{label}}
{{/tags}}