No-I/O dirty throttling [LWN.net]
This article brought to you by LWN subscribersSubscribers to LWN.net made this article — and everything that surrounds it — possible. If you appreciate our content, please buy a subscription and make the next set of articles possible. "Writeback" is the process of writing dirty pages back to persistent storage, allowing those pages to be reclaimed for other uses. Making writeback work properly has
Node.jsã¨éžåŒæœŸI/Oã¨æ··ä¹±ã—ãŸç§ - shutdown -r now
最近ã€Node.jsã«èˆˆå‘³ãŒã‚ã‚Šã¾ã™ã€‚Node.jsを調ã¹ã¦ã„ã‚‹ã¨ã€I/O関係ã§ã€éžåŒæœŸI/Oã€ãƒŽãƒ³ãƒ–ãƒãƒƒã‚ングã€ã‚³ãƒ¼ãƒ«ãƒãƒƒã‚¯ç‰ã€ã„ã‚ã„ã‚ã¨ã‚ーワードãŒã§ã¦ãã¦æ··ä¹±ã—ã¦ãã¾ã™ã€‚ ãã“ã§ã€ãƒ–ãƒã‚°ã«æ›¸ã„ã¦æ•´ç†ã—よã†æ€ã„ã¾ã™ã€‚é–“é•ã„ãŒã‚ã‚Œã°æ˜¯éžã€æŒ‡æ‘˜ã—ã¦ãã ã•ã„。 言葉ã®å®šç¾© â—‡éžåŒæœŸå‘¼ã³å‡ºã—（Asynchronous Call）ã¨åŒæœŸå‘¼ã³å‡ºã—（Synchronous Call）ã®é•ã„ åŒæœŸå‘¼ã³å‡ºã—（Synchronous Call） 通常メソッドを呼ã³å‡ºã™ã¨ãƒ¡ã‚½ãƒƒãƒ‰å†…ã®å‡¦ç†ãŒå®Œäº†ã™ã‚‹ã¾ã§ã€å‘¼ã³å‡ºã—å…ƒã«ã¯æˆ»ã£ã¦ã“ãªã„。ã“ã®ã‚ˆã†ãªãƒ¡ã‚½ãƒƒãƒ‰å‘¼ã³å‡ºã—ã®ã“ã¨ã€‚ éžåŒæœŸå‘¼ã³å‡ºã—（Asynchronous Call） メソッドを呼ã³å‡ºã—ãŸçž¬é–“ã«å‘¼ã³å‡ºã—å…ƒã«å‡¦ç†ãŒæˆ»ã£ã¦ãるよã†ãªå‘¼ã³å‡ºã—ã®ã“ã¨ã€‚éžåŒæœŸã§å‘¼ã³å‡ºã•ã‚ŒãŸãƒ¡ã‚½ãƒƒãƒ‰ã¯ã€ç’°å¢ƒã«ã‚ˆã£ã¦å‡¦ç†ã•ã‚Œã‚‹ã‚¿ã‚¤ãƒŸãƒ³ã‚°ãŒå¤‰ã‚る。 ◇マルãƒã‚¹ãƒ¬ãƒƒãƒ‰ï¼ˆmultithread
Techie Stuff › Understanding the code inside Tornado, the asynchronous web server
My goal here is to have a walk through the lower layers of the Tornado asynchronous web server. I take a bottom-up approach, starting with the polling loop and going up to the application layer, pointing out the interesting things I see on my way. So if you plan on reading the source code of the Tornado web framework, or you are just curious to see how an asynchronous web server works, I would
Anticipatory I/Oスケジューラ ãã®2 - Linuxカーãƒãƒ«ãƒ¡ãƒ¢
Anticipatory I/Oスケジューラ ã®ç¶šã。 Elevatorã¨ã®ã‚¤ãƒ³ã‚¿ãƒ•ã‚§ãƒ¼ã‚¹ Elavatorã‹ã‚‰å‘¼ã³å‡ºã•ã‚Œã‚‹Anticipatory I/Oスケジューラã®ãƒ«ãƒ¼ãƒãƒ³ç¾¤ã¯struct elevator_type iosched_as ã«å®šç¾©ã•ã‚Œã¦ã„る。 .elevator_merge_fn = as_merge æ—¢å˜Requestã®å¾Œã«ãƒžãƒ¼ã‚¸(BackMerge)ã§ãã‚‹å ´åˆã¯ELEVATOR_BACK_MERGEã‚’è¿”ã—ã€æ—¢å˜Requestã®å‰ã«ãƒžãƒ¼ã‚¸(FrontMerge)ã§ãã‚‹å ´åˆã¯ã€ELEVATOR_FRONT_MERGEã‚’è¿”ã™ã€‚ FrontMergeã®æ¤œç´¢ã«ã¯BIOã®çµ‚端Sectorã®æ¬¡ã®Sectorã‚’Keyã«RBTreeを検索ã—ã¦BIO→RequestãŒé€£ç¶šã‚»ã‚¯ã‚¿ã«ãªã‚‹RequestãŒãªã„ã‹æŽ¢ã™ã€‚ - as_find_arq_rb() BackMergeã®æ¤œç´¢ã«ã¯BIO
Iotop's homepage
Linux has always been able to show how much I/O was going on (the bi and bo columns of the vmstat 1 command). Iotop is a Python program with a top like UI used to show of behalf of which process is the I/O going on. It requires Python ≥ 2.7 and a Linux kernel ≥ 2.6.20 with the TASK_DELAY_ACCT CONFIG_TASKSTATS, TASK_IO_ACCOUNTING and CONFIG_VM_EVENT_COUNTERS options on.
bonnie++ 㧠I/O 性能を測定 （Linux/Unix ã§ã® IO ベンãƒãƒžãƒ¼ã‚¯ã‚½ãƒ•ãƒˆï¼‰
今ã¾ã§ Linux 上ã§ãƒãƒ¼ãƒ‰ãƒ‡ã‚£ã‚¹ã‚¯ã®ãƒ‘フォーマンスを計測ã™ã‚‹æ–¹æ³•ã¨ã—㦠hdparm を使ã£ã¦ãã¾ã—ãŸãŒã€ã‚‚ã†å°‘ã—ã„ã‚ã„ã‚ãªã‚±ãƒ¼ã‚¹åˆ¥ã«ãƒ‘フォーマンスを計測ã—ãŸã„ãªãーã¨ã‹ NFS ã®ãƒ‘フォーマンスを計測ã—ãŸã„ãªãーã¨ã‹æ€ã£ã¦ã€ãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯ãƒ„ールãŒãªã„ã‚‚ã®ã‹ã¨èª¿ã¹ã¦ã¿ãŸã‚‰ bonnie++ ã£ã¦ã®ã‚’知りã¾ã—ãŸã€‚ Bonnie++ now at 1.03e (last version before 2.0)! Bonnie++ is a benchmark suite that is aimed at performing a number of simple tests of hard drive and file system performance. Then you can decide which test is important and decide how to compa
Iometer project
Project [Team] [Get involved] [Donations] Software [Platforms] [Downloads] [Known Issues] [Screenshots] Resources [Documents] [Mailing Lists] [Links] As the Iometer User's Guide says, Iometer is an I/O subsystem measurement and characterization tool for single and clustered systems. It was originally developed by the Intel Corporation and announced at the Intel Developers Forum (IDF) on February 1
åˆæœŸåŒ–パラメータ filesystemio_options ã®å€¤ã«ã‚ˆã£ã¦I/Oã«é–¢ã™ã‚‹ã‚·ã‚¹ãƒ†ãƒ コールãŒã©ã®ã‚ˆã†ã«å¤‰åŒ–ã™ã‚‹ã‹ - ablog
æ–°ä¹…ä¿æµ©äºŒã•ã‚“ã®ãƒ–ãƒã‚°ã®ä»¥ä¸‹ã®ã‚¨ãƒ³ãƒˆãƒªã‚’èªã‚“ã§ã€è‡ªåˆ†ãªã‚Šã«ç†è§£ã—ãŸã“ã¨ã‚’ã¾ã¨ã‚ã¦ã¿ãŸã€‚ å°å¹¡ã•ã‚“ã€yohei-aã•ã‚“ã€wmo6hashã•ã‚“ãªã©ã€ã„ã‚ã„ã‚ã”æ„見ãŒã‚ã‚Šã¾ã—ãŸãŒã€ä¸€åº¦ã€Oracleã®éžåŒæœŸI/Oã®å®Ÿè£…ã¯ã©ã†ã ã£ãŸã®ã‹å†ç¢ºèªãŒå¿…è¦ã ã¨æ€ã„ã¡ã‚‡ã£ã¨èª¿ã¹ã¦ã¿ã¾ã™ã€‚ 手当ãŸã‚Šæ¬¡ç¬¬ã‚„ã£ã¦ã‚‚ã—ょã†ãŒãªã„ã®ã§ã€ä»¥ä¸‹ã®3ã¤ã®è¦³ç‚¹ã§èª¿æŸ»ã—ã¦ã¿ã¾ã™ã€‚多分ã€ä½•å›žã‹ã«åˆ†ã‘ã¦èª¿æŸ»ã™ã‚‹ã¨æ€ã†ã®ã§ã™ãŒã€ä»Šå›žã¯åˆæœŸåŒ–パラメータfilesystemio_options = [none|directio|asynch|setall]ã§ã©ã®ã‚ˆã†ã«I/Oã«é–¢ã™ã‚‹ã‚·ã‚¹ãƒ†ãƒ コールãŒå¤‰åŒ–ã™ã‚‹ã‹è¦‹ã¦ã¿ã¾ã™ã€‚ 10046 trace name context forever: Unbreakable Enterprise Kernelã®ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°ã¯éžåŒæœŸI/Oã‹? ã¾ã¨ã‚ åˆæœŸåŒ–パラメータfilesystemio_optio
Disk IO Benchmarking in the Cloud
This is the second post in our series on cloud server performance benchmarking. The previous blog post, What is an ECU? CPU Benchmarking in the Cloud, focused strictly on CPU performance. In this post, we’ll look at disk IO performance. Choosing a cloud provider should be based on a many factors including performance, price, support, reliability/uptime, scalability, network performance and feature
Storageã®ãƒ‘フォーマンスを調ã¹ã‚‰ã‚Œã‚‹ã€IOzone - UNIXçš„ãªã‚¢ãƒ¬
ストリーミングé…ä¿¡ã‚„DBã§ã®ä½¿ç”¨æ™‚ãªã©ã€ã‚·ã‚¹ãƒ†ãƒ ã®ãƒ‘フォーマンスを見ãŸéš›ã«StorageãŒãƒœãƒˆãƒ«ãƒãƒƒã‚¯ã«ãªã‚‹ã“ã¨ã¯å¤šã€…ã‚ã‚Šã¾ã™ã€‚ ã¾ãŸStorageã®ãƒ‘フォーマンスã¯HDDã®å›žè»¢æ•°ã‚„ã€ãƒ•ã‚¡ã‚¤ãƒ«ã®é…置方法ã€ã¾ãŸãƒ•ã‚¡ã‚¤ãƒ«ã‚·ã‚¹ãƒ†ãƒ ãªã©ã«ã‚‚ä¾å˜ã™ã‚‹ã®ã§ã€å…±é€šã—ãŸãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯ãƒ†ã‚¹ãƒˆãŒå¿…è¦ã«ãªã£ã¦ãã¾ã™ã€‚ 自分ã§ã€ddコマンドを使ã£ã¦ä½œæˆã—ã¦ã‚‚良ã„ã®ã§ã™ãŒä»Šå›žã¯æ‰‹è»½ã«ãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯è©¦é¨“ã‚’è¡Œã†ã“ã¨ãŒã§ãã‚‹ã€IOzoneを紹介ã—ãŸã„ã¨æ€ã„ã¾ã™ã€‚ IOzoneをダウンãƒãƒ¼ãƒ‰ã—ã¦ãる。 å…¬å¼ã‚µã‚¤ãƒˆã¯ä»¥ä¸‹ã«ãªã‚Šã¾ã™ã€‚ Iozone Filesystem Benchmark ã•ã¦ã“ã“ã‹ã‚‰å–å¾—ã—ã¦ã€ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã‚’ã—ã¾ã—ょã†ã€‚ # wget http://www.iozone.org/src/current/iozone3_283.tar # tar xvf iozone3_283.tar # cd iozone3_2
IO::Handle::Util
My friend miyagawa has been championing PSGI and its reference implementation, Plack. This is something we've needed for a long time: a clean and simple way to respond to HTTP requests without the cruft of CGI and %ENV. The PSGI specification requires the body of the response to be represented using an object similar to IO::Handle. I've released IO::Handle::Util, a convenience package designed to
ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ãƒ—ãƒã‚°ãƒ©ãƒ ã®I/O戦略 - sdyuki-devel
図解求む。 以下「プãƒãƒˆã‚³ãƒ«å‡¦ç†ã€ã¨ã€Œãƒ¡ãƒƒã‚»ãƒ¼ã‚¸å‡¦ç†ã€ã‚’分ã‘ã¦æ‰±ã£ã¦ã„ã‚‹ãŒã€ã“ã®å·®ãŒé¡•è‘—ã«å‡ºã‚‹ã®ã¯å…¨æ–‡æ¤œç´¢ã‚¨ãƒ³ã‚¸ãƒ³ã‚„éžåŒæœŸã‚¸ãƒ§ãƒ–サーãƒãƒ¼ãªã©ã€å°ã•ãªãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã§é‡ã„処ç†ã‚’ã™ã‚‹ã‚¿ã‚¤ãƒ—。ストリーム指å‘ã®ãƒ—ãƒãƒˆã‚³ãƒ«ã®å ´åˆã¯ã€Œãƒ—ãƒãƒˆã‚³ãƒ«å‡¦ç†ã€ã‚’「ストリーム処ç†ã€ã«ç½®ãæ›ãˆã‚‹ã¨ã„ã„ã‹ã‚‚ã—ã‚Œãªã„。 シングルスレッド･イベント駆動 コãƒã‚¯ã‚·ãƒ§ãƒ³N：スレッド１。epoll/kqueue/select を１ã¤ä½¿ã£ã¦ã‚¤ãƒ™ãƒ³ãƒˆãƒ«ãƒ¼ãƒ—を作る。 マルãƒã‚³ã‚¢CPUã§ã‚¹ã‚±ãƒ¼ãƒ«ã—ãªã„ã®ã§ã€ã‚µãƒ¼ãƒãƒ¼ã§ã¯ä»Šæ™‚ã“ã®ãƒ¢ãƒ‡ãƒ«ã¯æµè¡Œã‚‰ãªã„。 クライアントã§éžåŒæœŸãªãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãƒ³ã‚°ã‚’ã‚„ã‚ŠãŸã„å ´åˆã¯ã“ã®ãƒ¢ãƒ‡ãƒ«ã‚’使ãˆã‚‹ï¼š サーãƒãƒ¼ã«ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ã‚’é€ä¿¡ イベントãƒãƒ³ãƒ‰ãƒ©ã‚’登録；ã“ã®ã¨ãイベントãƒãƒ³ãƒ‰ãƒ©ã®ãƒã‚¤ãƒ³ã‚¿ã‚’å–ã£ã¦ãŠã イベントãƒãƒ³ãƒ‰ãƒ©->フラグ ãŒONã«ãªã‚‹ã¾ã§ã‚¤ãƒ™ãƒ³ãƒˆãƒ«ãƒ¼ãƒ—を回㙠イベントãƒãƒ³ãƒ‰ãƒ©->çµæžœ を返㙠１コãƒã‚¯ã‚·ãƒ§ãƒ³ï¼‘スレッ
How to set up Basic I/O Monitoring on Linux
This is my fourth week at Pythian and in Canada and I'm starting to get back to my normal life cycle --- my personal things are getting sorted and my working environment is set. Here at Pythian I'm in a team of four people together with Christo, Joe, and Virgil. (I should write another post about beginning at Pythian --- will do one day.) Yesterday, I asked Christo to show me how he monitors I/O o
iostat -x
My favorite Linux tool in DB work is ‘iostat -x’ (and I really really want to see whenever I’m doing any kind of performance analysis), yet I had to learn its limitations and properties. For example, I took 1s snapshot from a slightly overloaded 16-disk database box: avg-cpu: %user %nice %system %iowait %steal %idle 8.12 0.00 2.57 21.65 0.00 67.66 Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s \ sda
fioを用ã„ãŸãƒ‡ã‚£ã‚¹ã‚¯IOã®ãƒ‘フォーマンス測定 | OSDN Magazine
コンピュータを構æˆã™ã‚‹ä¸»è¦ã‚³ãƒ³ãƒãƒ¼ãƒãƒ³ãƒˆã®ä¸ã§ã‚‚ã€ã‚¹ãƒˆãƒ¬ãƒ¼ã‚¸ç³»ã®ãƒ‘フォーマンスã¯ä»–ã«æ¯”ã¹ã¦ã‹ãªã‚ŠåŠ£ã‚‹ã‚‚ã®ã¨ãªã£ã¦ãŠã‚Šã€ä¾‹ãˆã°ãƒãƒ¼ãƒ‰ãƒ‡ã‚£ã‚¹ã‚¯ã¯å®¹é‡çš„ã«ã¯é †èª¿ã«æ‹¡å¤§ã—続ã‘ã¦ã„ã‚‹ã‚‚ã®ã®ã€ãã®ã‚¢ã‚¯ã‚»ã‚¹é€Ÿåº¦ã®ç™ºå±•ãƒšãƒ¼ã‚¹ã¯RAMã‚„CPUã®é€Ÿåº¦å‘上ã«è¿½ã„ã¤ã‘ãªããªã£ã¦ã„る。ã“ã†ã—ãŸãƒãƒ¼ãƒ‰ãƒ‰ãƒ©ã‚¤ãƒ–ã®æ€§èƒ½çš„é™ç•ŒãŒã‚·ã‚¹ãƒ†ãƒ パフォーマンスã®ãƒœãƒˆãƒ«ãƒãƒƒã‚¯ã¨ãªã£ã¦ã„ã‚‹å¯èƒ½æ€§ã‚’考ãˆãŸå ´åˆã€å„自ã®æ‰€æœ‰ã™ã‚‹ãƒ‡ã‚£ã‚¹ã‚¯ã‚„ファイルシステムãŒç™ºæ®å¯èƒ½ãªé€Ÿåº¦ãŠã‚ˆã³ã€ãƒ‡ã‚£ã‚¹ã‚¯ã®ã‚µãƒ–システムã«å¯¾ã—ã¦ãƒ¦ãƒ¼ã‚¶ãŒè¡Œãˆã‚‹è¨å®šå¤‰æ›´ã®å½±éŸ¿ã‚’数値的ã«æŠŠæ¡ã—ã¦ãŠãã“ã¨ã¯é‡è¦ãªæ„味を帯ã³ã¦ã„ã‚‹ã¯ãšã§ã‚る。ã¾ãŸãƒ‡ã‚£ã‚¹ã‚¯ã®ã‚¢ã‚¯ã‚»ã‚¹é€Ÿåº¦ã‚’å‘上ã•ã›ã‚‹æ‰‹æ³•ã®1ã¤ã¨ã—ã¦ã¯ã€RAID-5ã®ã‚ˆã†ã«è¤‡æ•°ã®ãƒ‡ã‚£ã‚¹ã‚¯ã‚’組ã¿åˆã‚ã›ã¦é‹ç”¨ã™ã‚‹ã“ã¨ãŒè€ƒãˆã‚‰ã‚Œã‚‹ã€‚ Linuxã®å ´åˆã€ç‰©ç†ãƒ‡ã‚£ã‚¹ã‚¯ã«å¯¾ã™ã‚‹ã‚¢ã‚¯ã‚»ã‚¹é€Ÿåº¦ã®åŸºæœ¬çš„ãªæƒ…å ±ã§ã‚ã‚Œã°ã€hdparmツールã«-TãŠã‚ˆã³-tオプション
アジアã®ãƒšãƒ³ã‚®ãƒ³: Linuxã¨Linuxã§åƒã人ãŸã¡(1)：ãŠå®¢æ§˜ãƒ»ä¸Šå¸ã«åˆã‚ã›ãŸI/Oスケジューラーã®é¸ã³æ–¹
ã“ã‚“ã°ã‚“ã¯ã€æŸHæ°ãŒä¸å›½ã«å‡ºå¼µã«è¡Œã£ã¦ã—ã¾ã£ãŸã›ã„ã§ã€ä»–グループã‹ã‚‰ã®å•ã„åˆã‚ã›ãƒ©ãƒƒã‚·ãƒ¥ã«æ‰ã¾ã‚Œã€å°‘々疲れ気味ã®rkã§ã™ã€‚ タイトルã¨çµ¡ã¾ã™ã¤ã‚‚ã‚Šã¯ãªã‹ã£ãŸã®ã§ã™ãŒã€Linuxã‚„PCã®ä¸–ç•Œã«ã„ã‚‹ã¨ã€ã“れらã®ã‚·ã‚¹ãƒ†ãƒ ãŒäººé–“社会ã®æ–¹æ³•ç†è«–ã«åŸºã¥ã„ã¦ä½œã‚‰ã‚Œã¦ã„ã‚‹ã“ã¨ãŒå«Œã§ã‚‚分ã‹ã£ã¦ãã‚‹ã‚‚ã®ã§ã™ã€‚ 仕事ã¯ãŽã‚ŠãŽã‚Šã¾ã§é…らã›ã‚‹ã®ãŒã‚ˆã„ã¯ãšãªã®ã«(é…延書ãè¾¼ã¿)ã ã¨ã‹ã€ç–‘å•ã«æ€ã†ã“ã¨ã‚‚ã‚ã‚Šã¾ã™ãŒ...(人間ã®è¨˜æ†¶ã¯æ®ç™ºã—ã¾ã™...) ã•ã¦ã€çš†ã•ã‚“ã®ä¼šç¤¾ã«ã¯ã©ã‚“ãªä¸Šå¸ãŒã„ã¾ã™ã‹ï¼Ÿã‚ã‚‹ã„ã¯ã©ã‚“ãªãŠå®¢æ§˜ã¨ã®ãŠä»˜ãåˆã„ãŒã‚ã‚Šã¾ã™ã‹ï¼Ÿ rkã‚‚ã€ã•ã¾ã–ã¾ãªä¸Šå¸ã€ã•ã¾ã–ã¾ãªãŠå®¢æ§˜ã¨ã®ãŠä»˜ãåˆã„ãŒã‚ã‚Šã¾ã—ãŸãŒã€(未ã 部下ã¨ã„ã†ã‚‚ã®ã¯ã‚ã‚Šã¾ã›ã‚“) 人ã«ã‚ˆã‚Šã•ã¾ã–ã¾ãªä»•äº‹ã®ä»•æ–¹ã‚’è¦æ±‚ã—ã¦ãã¾ã™ã€‚ rkã¯ä¸€å¿œã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã§ã™ã®ã§ã€å†…勤をä¸å¿ƒã¨ã—ã¦ã„ã‚‹æ¥å‹™å½¢æ…‹ã§ã™ã€‚ãã‚Œã§ã‚‚上å¸ãŒå¤‰ã‚ã‚‹ãŸã³ã«ç§ã®ã‚¹ã‚±ã‚¸ãƒ¥ãƒ¼ãƒ«ã¸ã®æ–‡å¥ã®ã¤ã‘æ–¹ãŒå¤‰
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
The Linux Kernel's VFS Layer
ã„ã„åŠ æ¸›ãªblog (Kurosaka)
http://ekschi.com/technology/2009/08/24/vdbench-%E3%81%A7%E3%83%87%E3%82%A3%E3%82%B9%E3%82%AF%E3%81%AE%E6%80%A7%E8%83%BD%E3%82%92%E6%B8%AC%E5%AE%9A%E3%81%99%E3%82%8B/
Fast, Simple I/O Concurrency For Ruby Ruby ã®ãŸã‚ã®ã€é«˜é€Ÿãƒ»ç°¡å˜ãªä¸¦è¡Œ Io: Rubykaigi2009 | PDF | Thread (Computing) | Scheduling (Computing)
{{#tags}}- {{label}}
{{/tags}}