2 ms·
I'm not sure benchmarks of nginx v. Apache are enough to definitively settle that asynchronous programming is better than synchronous programming. This USENIX p
by _delirium 17y ago
I'm not sure benchmarks of nginx v. Apache are enough to definitively settle that asynchronous programming is better than synchronous programming. This USENIX paper argues the opposite, though it admits there are some problems with current thread-based solutions: http://www.usenix.org/events/hotos03/tech/full_papers/vonbehren/vonbehren_html/ http://www.usenix.org/events/hotos03/tech/full_papers/vonbeh...
- staunch 17y agoNo one has created a web server that's anywhere near competing with nginx (or similar) on performance/efficiency. I think that counts as proof that in practice the argument is settled. Theoretically I'm sure it's not settled.
- _delirium 17y agoThe post complains about the inadequacy of current language support for asynchronous programming, though, while the linked paper argues that the real problem is the inadequacy of current language support for synchronous programming. Admittedly, they're talking about different kinds of "support": it's harder to do asynchronous programming in a lot of languages, but it's even harder than that to do synchronous programming efficiently, because the toolchains don't support the optimizations that would be necessary (but which you can do by hand in an asynchronous programming style).