NGINX 1.9ãŒæ±Žç”¨TCPサーãƒã¨ã—ã¦ä½¿ãˆã‚‹ã‚ˆã†ã«ãªã£ã¦ã„ãŸä»¶ - QiitaDeleted articles cannot be recovered. Draft of this article would be also deleted. Are you sure you want to delete this article?
main
コンテンツã¸ã‚¹ã‚ップ 登録ã¯ç„¡åŠ¹åŒ–ã•ã‚Œã¾ã—ãŸã€‚
Tuning TCP and NGINX on EC2
Chartbeat measures and monetizes attention on the web. They were experiencing slow load times and TCP retransmissions due to default system settings. Tuning various TCP, NGINX and EC2 ELB settings like increasing buffers, disabling Nagle's algorithm, and enabling HTTP keep-alive resolved the issues and improved performance. These included tuning settings like net.ipv4.tcp_max_syn_backlog, net.core
Nginx Optimization: understanding sendfile, tcp_nodelay and tcp_nopush
This article a is translation by popular request of Optimisations Nginx, bien comprendre sendfile, tcpnodelay et tcpnopush I wrote in French in January. Most articles dealing with optimizing Nginx performances recommend to use sendfile, tcp_nodelay and tcp_nopush options in the nginx.conf configuration file. Unfortunately, almost none of them tell neither how they impact the Web server nor how the
Part 1: Lessons learned tuning TCP and Nginx in EC2 « Chartbeat Engineering Blog
Part 1: Lessons learned tuning TCP and Nginx in EC2 January 2nd, 2014 by Justin Our average traffic at Chartbeat has grown about 33% over the last year and depending on news events, we can see our traffic jump 33% or more in a single day.  Recently we’ve begun investigating ways we can improve performance for handling this traffic through our systems.  We set out and collected additional metrics f
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}