[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why Events Are A Bad Idea (for High-concurrency Servers)
- To: Java-Threads Mailing List <java-threads@xxxxxxxxxx>, occam-com mailing list <occam-com@xxxxxxxxxx>
- Subject: Why Events Are A Bad Idea (for High-concurrency Servers)
- From: "Beton, Richard" <richard.beton@xxxxxxxxxx>
- Date: Tue, 10 Jun 2003 15:53:25 +0100
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
Something for discussion:
Paper presented at Usenix HotOS 2003, conference on hot topics in OS.
"Event-based programming has been highly touted in recent years as the
best way to write highly concurrent applications. Having worked on
several of these systems, we now believe this approach to be a mistake.
Specifically, we believe that threads can achieve all of the strengths
of events, including support for high concurrency, low overhead, and a
simple concurrency model. Moreover, we argue that threads allow a
simpler and more natural programming style."
100,000 user level threads in a web server, achieving high performance.
Compiler support for concurrency is deemed desirable, a fruitful
An interesting follow-up to Ousterhout's 1996 Usenix talk "Why threads
are a bad idea (for most purposes)".
Registered Office: Roke Manor Research Ltd, Siemens House, Oldbury, Bracknell,
Berkshire. RG12 8FZ
The information contained in this e-mail and any attachments is confidential to Roke
Manor Research Ltd and must not be passed to any third party without permission. This
communication is for information only and shall not create or change any contractual