Both the Python gevent/ws4py implementation and the Node.js websocket implementation failed hard with around half of the connections hitting the 2 second TCP connection timeout. I expected Go to kick Erlang's ass in the performance department but the message latency was much higher than Erlang's latency and we had 225 unhappy customers. Go only reached C9.775k; close but no cigar. I did not know w
node.js+Socket.IOã§ãªã¢ã«ã¿ã¤ã ã¢ããªã±ã¼ã·ã§ã³ãä½ããããã ãã©ãWebSocket使ãã«ãã¦ãXHR-Polling使ãã«ãã¦ããµã¼ãçµç±ãã¦éä¿¡ãã¦ããã°å½ç¶ã¿ã¤ã ã©ã°ã¯ããããã§ãããã£ã¦ã©ããããé 延ãããã®ãªãã ããï¼ ã¨æã£ã¦ããããªãµã¼ãã§è©¦ãã¦ã¿ã(追è¨ãã¾ãã)ã 測å®æ¹æ³ var server = require('http').createServer(function (req, res) { require('data-section').get('html', function (err, data) { res.writeHead(200, { 'Content-Type': 'text/html' }); res.end(data); }); }); var io = require('socket.io').listen(server);
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}