re: memory use If the number of concurrent requests is small, then the memory used by thread per request is usually not an issue.
When implementing long polling, the number of concurrent requests can be very large. Sharing threads between requests in a long polling server can result in significant memory savings. re: advantages of evented servers There are also disadvantages to an evented server. Writing logic in a series of callbacks is more difficult to understand and debug than the sequential code used in a thread per request model. re: throughput of Netty/Aleph vs. Jetty The difference in throughput between Aleph/Netty and Jetty might not be a result of the different threading models. It might be that Jetty has more goop in it than Netty (I don't know if this is true or not). This blog post presents data showing that threading is faster than NIO: http://mailinator.blogspot.com/2008/02/kill-myth-please-nio-is-not-faster-than.html -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
