How TCP backlog works in Linux
When an application puts a socket into LISTEN state using the listen syscall, it needs to specify a backlog for that socket. The backlog is usually described as the limit for the queue of incoming connections. Because of the 3-way handshake used by TCP, an incoming connection goes through an intermediate state SYN RECEIVED before it reaches the ESTABLISHED state and can be returned by the accept s
somaxconnã®ä¸Šé™å€¤ã¯65535
Linuxã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ‘ラメータã®ä¸€ã¤ã«ã€net.core.somaxconnã¨ã„ã†ã®ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯listen(2)ã®ç¬¬äºŒå¼•æ•°backlogã®ä¸Šé™å€¤ã¨ãªã£ã¦ã„ã¾ã™ã€‚ã“ã®somaxconnã¯ä¸€è¦‹intã«è¦‹ãˆã¾ã™ãŒã€å®Ÿã¯unsigned shortã®ç¯„囲ã®æ•°å€¤ã—ã‹å—ã‘付ã‘ã¾ã›ã‚“。ãれを超ãˆã‚‹æ•°å€¤ã‚’入れるã¨é»™ã£ã¦åˆ‡ã‚Šæ¨ã¦ã‚‰ã‚Œã¾ã™ã€‚ã¤ã¾ã‚Š -1→65535 0→0 65535→65535 65536→0 65537→1 ã¨åŒã˜ã‚ˆã†ãªå‹•ä½œã‚’内部的ã«ã—ã¾ã™ã€‚ãªã®ã§ã€ã“ã®å€¤ã¯çµ¶å¯¾ã«0～65535ã®ç¯„囲を超ãˆã¦ã¯ã„ã‘ã¾ã›ã‚“。以下ã€è©³ã—ã„説明ã§ã™ã€‚ ãŠã“ã¨ã‚ã‚Š: ã“ã®ä»•æ§˜ã¯Linux 3.11以é™å¤‰æ›´ã•ã‚Œã¦ãŠã‚Šã€ç¯„囲外ã®æ•°å€¤ã‚’è¨å®šã§ããªã„よã†ã«ãªã£ã¦ã„ã¾ã™ã€‚ã“ã“ã«æ›¸ã„ã¦ã‚る内容ãŒå†ç¾ã™ã‚‹ã®ã¯ã€Linux 3.10以å‰ã®å¤ã„カーãƒãƒ«ã®ã¿ã§ã™ã€‚ ã¾ãšsysctlã®å®šç¾©ã§ã™ãŒ net/core/sysct
prefork サーãƒãƒ¼ã¨ thundering herd å•é¡Œ - naoyaã®ã¯ã¦ãªãƒ€ã‚¤ã‚¢ãƒªãƒ¼
Catalyst ã‚’ POE ã§å‹•ã‹ã™ Engine ã® Catalyst::Engine::HTTP::POE ã¨ã„ã†å®Ÿè£…㌠CPAN ã«ã‚ã‚Šã¾ã™ã€‚"Single-threaded multi-tasking Catalyst engine " ã ãã†ã§ã™ã€‚"Single-threaded" ã¨è¨€ã„ã¤ã¤ã‚‚実装を覗ã„ã¦ã¿ã‚‹ã¨ç’°å¢ƒå¤‰æ•° CATALYST_POE_MAX_PROC ã‚’ 1 よりも大ããè¨å®šã™ã‚‹ã“ã¨ã§ prefork ã™ã‚‹å®Ÿè£…ã«ãªã£ã¦ã¾ã™ã€‚POEシングルスレッドã§ã¯ã‚¢ãƒ—リケーション内ã§ç™ºç”Ÿã™ã‚‹ãƒ–ãƒãƒƒã‚¯ã‚’é¿ã‘ã‚‹ã“ã¨ãŒé›£ã—ã„ã®ã§ãã®ãŸã‚ã®å®Ÿè£…ã˜ã‚ƒãªã„ã‹ãªã¨æ€ã„ã¾ã™ã€‚ ã¨ã“ã‚ã§ã“ã® Catalyst POE エンジンã€prefork ã®å®Ÿè£…ã¯ã©ã®ã‚ˆã†ã«è¡Œã£ã¦ã„ã‚‹ã‹ã¨ã„ã†ã¨ POE ã‹ã‚‰ prefork ã¨åã®ä»˜ã„ãŸã‚¤ãƒ™ãƒ³ãƒˆãŒç™ºç”Ÿã™ã‚‹ã¨ãŠã‚‚ã‚€ã‚ã«åプãƒã‚»ã‚¹ã‚’生æˆã™ã‚‹ã€ã¨ã„ã†ã®ã‚‚ã®ã€‚複数ã®
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}