IBM Developer is your one-stop location for getting hands-on training and learning in-demand skills on relevant technologies such as generative AI, data science, AI, and open source.
I did a keynote presentation at the SIGCOMM'15 HotMiddlebox workshop, "Mobile TCP optimization - Lessons Learned in Production". The title was set before I had any idea of what I'd really be talking about, just that it'd be about some of the stuff we've been working on at Teclo. So apologies if the content isn't an exact match for the title. This post contains my slides, interleaved with my speake
New! OâReilly announces launch of the AI Academy. Read now Introducing the AI Academy Help your entire org put GenAI to work Every employee today needs to know how to prompt GenAI, use it to enhance critical thinking and productivity, and more. With the AI Academy they can. For less. OâReilly AI-powered Answers just got even smarter OâReilly Answers instantly generates information teams can trust,
mTCP enables high-performance userspace TCP/IP stacks by bypassing the kernel and reducing system call overhead. It was shown to achieve up to 25x higher throughput than Linux for short flows. The document discusses porting the iperf benchmark to use mTCP, which required only minor changes. Performance tests found that mTCP-ified iperf achieved similar throughput as Linux iperf for different packe
listen()ã®backlogãä¸è¶³ããéã®TCP_DEFER_ACCEPTã®åä½ã«ã¤ã㦠- blog.nomadscafe.jpã¨ããè¨äºã®ä¸ã§ãlisten backlog ãããµããå¾ã« accept(2) ããã¨ããã®å¾ã® read(2) ã EAGAIN ãè¿ããããæ¥ç¶ãä¸å®å®ã«ãªãã¨ããäºè±¡ã説æããã¦ãã¾ãããæ°ã«ãªã£ãã®ã§èª¿ã¹ã¦ã¿ããã¨ãã¾ã¨ãã¾ãã çµè«ããè¨ãã¨ããã¯Linuxã®ä»æ§ã§ããmanã®tcp(7)ãè¦ãã¨ã TCP_DEFER_ACCEPT (since Linux 2.4) Allow a listener to be awakened only when data arrives on the socket. Takes an integer value (seconds), this can bound the maximum number of
æ¨å¹´æ«ãããã£ã¨ãããªãã¨ããã¦ã¾ãã¦ããã®ææã«ãªã£ã¦ããããä»å¹´åã®ããã°è¨äºã§ãã é²æçãªã¢ã¬ãã¢ã¬ã§ããããªããããããã3å¹´ç®ã«çªå ¥ã® @pandax381ã§ãã RTT > 100ms ã¨ã®æ¦ã çµç·¯ã¯ãã®ã¸ãã¨ãè¦ã¦ããã ããã¨ãããã¾ãããæ¥æ¬ã¨æµ·å¤ã®éãçµã¶é·è·é¢ãããã¯ã¼ã¯ï¼ããããLong Fat pipe Networkï¼ã«ããã¦ãéä¿¡æéãåæ¸ããã«ã¯ã©ãããããããï¼ãã¨ãããã¨ããæ¨å¹´æ«ããããããã£ã¨ã¢ã¬ã³ã¬ãã£ã¦ãã¾ããã éä¿¡ãããã±ãããç¸æã«å°éããã¾ã§ã®æéï¼ä¼éé 延ï¼ãåæ¸ããã®ã¯ãå ãã¡ã¤ãã¼ã®å¹çã®ç 究ã¨ãããªãã¨ç©ççã«ç¡çãªã®ã§ãããã§è¨ãéä¿¡æéã¨ã¯ãTCPéä¿¡ãã«ãããä¸é£ã®éä¿¡ãå®äºããã¾ã§ã®æéã§ãã ä¼éé 延ã«ã¤ãã¦ã¯ãæ¥æ¬å½å ã®ãã¹ãå士ã§ããã°ãRTTï¼å¾å¾©é 延æéï¼ã¯ã ããã10ã30msç¨åº¦ã§ãããæ¥æ¬ã»åç±³éã ã¨10
Linuxï¼OSã®tcpã¿ã¤ã ã¢ã¦ãã®ããã©ã«ãå¤ã«ã¤ã㦠â ä¾ãã°ãcurlã使ç¨ãã¦ãã¿ã¤ã ã¢ã¦ãå¤ã300ç§ã«æå®ããã¿ã¤ã ã¢ã¦ããããããç¡ããã¨ããã¦ããå®é180ç§ãè¶ ãããããã§ã¿ã¤ã ã¢ã¦ãããäºè±¡ãçºçãã¦ãã¾ããã ããããcurlã ããããªãã¦ãä¾ãã°apacheã®mod_proxy_balancerã®ããã¯ã¨ã³ããµã¼ãã¸ã®ã¿ã¤ã ã¢ã¦ãã«ã¤ãã¦ããã¿ã¤ã ã¢ã¦ãå¤ã300ç§ã¨ãã§ãã£ã¦ããã¦ããå®éã¯180ç§ã¡ããã§ã¿ã¤ã ã¢ã¦ããã¦ãã¾ã£ã¦ãã¾ããã ããã«ã¤ãã¦ãã¡ãã£ã¨èª¿ã¹ãã¨ããã©ããLinuxã®OSã¨ãã¦æã£ã¦ããTCPã®ã¿ã¤ã ã¢ã¦ãå¤ãå¹ãã¦ããããã ãã¨ãããã¨ããããã¾ããã ãããè¦ãã¨åããã¾ãã #cat /proc/sys/net/ipv4/tcp_syn_retries 5 ããã¯tcpã®synãéä¿¡ãããªãã©ã¤åæ°ã¿ããã§ã以ä¸ã®ãã¸ãã¯ã§ãªã
HPC TCP/IP 2009 5 29 SACSIS2009 HPC TCP/IP 2 ⢠⢠1 Gbps RTT 100 ⢠240 Mbps ⹠⢠940 Mbps ⺠(2) HPC TCP/IP ⢠Ethernet PC ⢠TCP/IP 2 10MB 3 0 200 400 600 800 1000 0 100 200 300 400 500 600 Bandwidth (Mbps) Time (msec) 160 0 200 400 600 800 1000 0 100 200 300 400 500 600 Bandwidth (Mbps) Time (msec) x3.5 (2) ⢠TCP/IP ⢠⢠MPI ⢠TCP/IP TCP ⢠TCP Reno [RFC2851] ⢠TCP CUBIC Compound TCP 4 (3) ⢠TCP/IP ⢠T
In data communications, the bandwidth-delay product is the product of a data link's capacity (in bits per second) and its round-trip delay time (in seconds).[1] The result, an amount of data measured in bits (or bytes), is equivalent to the maximum amount of data on the network circuit at any given time, i.e., data that has been transmitted but not yet acknowledged. The bandwidth-delay product was
SPDYãQUICç»å ´ã®èæ¯ãWebã®é²åããããã³ã«ãå¤ãã¤ã¤ãããHTML5 Conference 2013 Webãããéããããã¨ãHTTPãããåªãããããã³ã«ã¨ãã¦ææ¡ãããSPDYï¼ã¹ãã¼ãã£ï¼ãããããã®SPDYã«ãã£ã¦ãä¸ä½ã¬ã¤ã¤ã§ããTCPã®å¶éãé¡èã«è¦ããããã«ãªã£ã¦ãã¾ãããã®ãã¨ã§TCP以å¤ã®ãããã³ã«ã¨ãã¦QUICãGoogleãææ¡ãã¦ãã¾ãã Webã®é²åã¯ãã¤ã³ã¿ã¼ãããã®ãããã³ã«ã«ã¾ã§å½±é¿ãä¸ãããã¨ãã¦ãããã¨ããé常ã«èå³æ·±ã話ããHTML5ã®ã³ãã¥ããã£ãhtml5jã主å¬ã®ã¤ãã³ããHTML Conference 2013ãã§è¡ãããå°æ¾å¥ä½æ°ã®ã»ãã·ã§ã³ãææ°Webãããã³ã«ãå¾åã¨å¯¾çãã§è¡ããã¾ããã ãã®å 容ããã¤ã¸ã§ã¹ãã§ç´¹ä»ãã¾ãããã ææ°Webãããã³ã«ãå¾åã¨å¯¾ç å°æ¾ã§ããæå±ã¯NTTã³ãã¥ãã±ã¼ã·ã§ã³ãºã§HTML5ã®ç 究
ã¨ãããã¨ã«ã(ä»æ´ï¼)æ°ä»ããã話ã§ãã HAãçµãã éã®VIPã®åãæ¿ããã¹ãããã£ã¦ããã¨ãã«ãé«è² è·æã¨ãã¯åãæ¿ãã«7ç§ã´ã£ãããããã±ã¼ã¹ã¨ãããã£ã¦ã7ç§ã£ã¦ä½ã®æ°åã ããã¨çåãæã¡ã¾ããã OSã¯ãCentOS 6.4(2.6.32-358.23.2.el6.x86_64)ã§ãã TCP SYNã®åéééãã1...2...4...ç§ã«ãªã£ã¦ãã ã§ãtcpdumpãçºãã¦ããã¨ä»¥ä¸ã®ãããªã·ã¼ã±ã³ã¹ã§ãã 11:50:35.689301 IP client-host.8957 > server-host.http: Flags [S], seq 1616681830, win 14600, options [mss 1460,sackOK,TS val 889880946 ecr 0,nop,wscale 7], length 0 11:50:36.688503 IP
Created by Vic Metcalfe, Andrew Gierth and other contributers (Transrated into Japanese by: Keisuke Mori)May 21, 1998 ãã®ææ¸ã¯ãUNIX ä¸ã§ã® ã½ã±ããã¤ã³ã¿ã¼ãã§ã¼ã¹ãç¨ãã TCP/IP ã¢ããªã±ã¼ã·ã§ã³ããã°ã©ãã³ã°ã«ã¤ãã¦ãé »ç¹ã«è¡ããã質åã¨ã㮠解çãéãããã®ã§ãã 1. ä¸è¬çãªæ å ±ã¨æ¦å¿µ 1.1 æ´æ°æ å ± 1.2 ãã® FAQ ã«ã¤ã㦠1.3 ãã® FAQ ã¯ã©ã®ãããªäººåãã§ãããã? 1.4 ã½ã±ããã£ã¦ä½ã§ãã? 1.5 ã½ã±ããã¯ã©ã®ããã«åä½ããã®ã§ãããã? 1.6 [ããæ¬ã®é¡å] ã¨ããæ¬ã®ã½ã¼ã¹ã³ã¼ãã¯ã©ãããåå¾ã§ãã¾ãã? 1.7 ã©ãã§ãã£ã¨æ å ±ãå¾ããã¨ãã§ãã¾ãã? 2. ã¯ã©ã¤ã¢ã³ãã¨ãµã¼ã(TCP/SOCK_STREA
TCPéä¿¡ãããããã°ã©ã ãæ¸ãéã«ããã¼ã¿ã®éä¿¡ã¯ã¾ã¨ãã¦ï¼åã§ãè¡ãã¹ããã¨ããã®ã¯éåã¨è¨ã£ã¦ãããã¨æãã¾ãããã®çç±ã¨ãã¦ã¯ããã±ããæ°ãæå°éã«æãããã¨ã§ãªã¼ãã¼ããããå°ãªãããããã ã¨ä¸è¬ã«èª¬æããã¾ãããèªåã¯ããã²ã¨ã¤ãã¤ã³ããããã¨èãã¦ãã¾ãã次ã®ã°ã©ããè¦ã¦ãã ããã ã°ã©ãã¯ãä¸å®éã®ãã¼ã¿ã転éããã®ã«ãããæéã¨ä½¿ç¨ãããããã¯ãµã¤ãºï¼ï¼åã®write(2)ã§æ¸ãè¾¼ããµã¤ãºï¼ã®é¢ä¿ã表ãããã®ã§ã注1ã ãã¹ãéã®TCPéä¿¡ãè¡ã£ã¦ããå ´åã¯ãTCPã®ãããã¡ãæå¹ã«æ©è½ããã®ã§ããããã¯ãµã¤ãºï¼ï¼ãã±ããæ°ã®éæ°ï¼ã«ããé度ã®å¤åã¯ãã»ã¼ããã¾ãããä¸æ¹ãåä¸ãã¹ãä¸ã§éä¿¡ãè¡ãã¨ããããã¯ãµã¤ãºã¨åæ¯ä¾ãã¦æè¦æéãåæ¯ä¾ã®é¢ä¿ã«ãããã¨ããããã¾ãã åå ã¯ãåä¸ãã¹ãä¸ã®éä¿¡ã§ã¯ãéä¿¡ããã»ã¹ãwrite(2)ãå¼ã¶ãã³ã«ã³ã³ãã¯ã¹ãã¹ã¤ãããçºç
iOS 7ã§MPTCP(Multipath TCP)ããµãã¼ããããã ((Apple iOS 7 surprises as first with new multipath TCP connections)) åçª ((ãããå®ã¯IETF87ã§ãanonymous OSãå®è£ ãã¦ããã¨ãã話ããããiOS 7ãããã ã£ãã®ãã¨ç´å¾ãã訳ã ã))ãªã®ã ãåã®å士課ç¨ã«ãããç 究ãã¼ãã§ãããå ã®IETFã§å¤§äººãã¡ã«ã¡ãã¿ã¡ã¿ã«ãããã®ãæããã®ã§MPTCPã«ã¤ãã¦èª¬æãã¦ãä½ãåºæ¥ãããã«ãªãããæ¸ãããã¨æãã MPTCPã¨ã¯ç°¡åã«ããã¨TCPã¹ããªã¼ã ãè¤æ°ã®çµè·¯ã§è»¢éãããã¨ã«ãããã¹ããªã¼ã ã®å¤éåã»èé害æ§ã®åä¸ãå³ããããã³ã«ã§ããã ãã®ã¿ã¤ãã³ã°ã§ãªããããããããã³ã«ãå¿ è¦ãç°¡åã«èª¬æãããã åãã使ãã¢ããªã±ã¼ã·ã§ã³ã¯å¤§æµTCPãç¨ãã¦éä¿¡ããã¦ãããããã¯é·ãã¤ã³ã¿
Nagleã¢ã«ã´ãªãºã ï¼ãã¼ã°ã«ã¢ã«ã´ãªãºã ãNagleâs algorithmï¼ã¯ãTCP/IP ãããã¯ã¼ã¯ã§éä¿¡ããªããã°ãªããªããã±ããæ°ãæ¸ãããå¹çæ§ããããããã®ã¢ã«ã´ãªãºã ã§ãããã¸ã§ã³ã»ãã¼ã°ã« (John Nagle) ããåã¥ããããã Nagleã1984å¹´ã«æ¸ããRFCæç« ãCongestion Control in IP/TCP Internetworks (RFC 896) ã§ã¯ãå½¼ããå°ããªãã±ããåé¡ãã¨å¼ã¶ãã¢ããªã±ã¼ã·ã§ã³ãç¹°ãè¿ã1ãã¤ããªã©å°ããªç²åº¦ã§éä¿¡ããåé¡ãåãä¸ãã¦ãããIPv4 㧠20ãã¤ããTCPèªä½ã§20ãã¤ãã®ãããã¼ããããåè¨40ãã¤ãã«ãªãããã1ãã¤ããéä¿¡ããã®ã«åè¨41ãã¤ãéä¿¡ããªãã¦ã¯ãªããªãããªã¼ãã¼ãããã大ãããããã¯ãTelnet ã»ãã·ã§ã³ãªã©ã§ããçºçãããã¼æä½ã1ãã¤ãã®ãã¼ã¿ãçæããå³æã«éä¿¡
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}