Threads without Locks
Russ Cox http://swtch.com/~rsc/talks/ Second International Plan 9 Workshop December 2007 Introduction Two popular camps for designing concurrent programs. Threads with locks Birrell, “An introduction to programming with threads” Top-level select loops with events Ousterhout, “Why threads are a bad idea (for most purposes)” Should we use threads or events? Andrew Birrell: threads. John Ousterhout:
Libtorrent experience - the poor state of async disk IO | Hacker News
My experience with Linux and buffered IO (ext4) from multiple threads has been very positive. The only beef I have is that you can't prevent the data you write/read from polluting the cache without resorting to madvise which isn't available from Java. I don't usually care about the contents of the page cache so it isn't a showstopper.You can do hundreds of thousands of random reads a second from a
Tech Notes: Nonblocking disk IO
It's natural, when writing an event-driven application, to want to perform disk operations like file reads and writes in the same non-blocking manner you use for sockets. This turns out to be hard. In theory there's POSIX AIO, but it's reported to not really work on Linux (my info might be out of date). Async libraries like node.js use an internal thread pool to simulate its desired event-behavior
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - postrank-labs/goliath: Goliath is a non-blocking Ruby web server framework
Loading...
