5 ms·
What is interesting here is to compare this one man's effort with "ancient tools" well-researched by two generations of old-school programmers with that amateur
by dschiptsov 12y ago
What is interesting here is to compare this one man's effort with "ancient tools" well-researched by two generations of old-school programmers with that amateurish hype and nonsense about node (author publicly stated in his blog that he has no experience with server side development on a POSIX system) and golang - a minimalist approach, carefully crafted by a rigorously trained "professionals". It is not just about KBs and milliseconds.
Btw, this "Hello world" example tells a little, basically, how efficiently memory allocation, and IO layer are implemented (that's why no one still could beat nginx).
Much more interesting comparison would be of some "real-world scenario", say, "implement an http look up for some public data-set, imported into a persistent local storage, say, Postgresql" and then compare not just throughput rates, but also resource usage.
- coldtea 12y ago>Btw, this "Hello world" example tells a little, basically, how efficiently memory allocation, and IO layer are implemented (that's why no one still could beat nginx). Actually at least on other guy just beat nginx just other day -- don't remember the name, it was some Japanese made server.
- lomnakkus 12y agoI think you might be thinking about Kazu Yamamoto and Mighttpd2? (Written in Haskell, incidentally.) I think this was the web server that beat out nginx on a largish number of cores (42?). For the life of me I can't find the original paper with the comparison graph, otherwise I'd link to it... Anyway, a lot of the performance work which went into mighttpd2 is automatically shared by all Haskell applications. (Most of it went to optimizing the GHC VM I/O Manager which handles I/O in the Haskell runtime. It's sort of like libev/libuv only at the VM level instead of as a library.)
- voxic11 12y agohttps://github.com/h2o/h2o https://github.com/h2o/h2o
- lomnakkus 12y agoI don't think that was the "Hey, look! Haskell beats nginx!" one, but very interesting nonetheless! :)
- codygman 12y agoPage 8: http://themonadreader.files.wordpress.com/2011/10/issue19.pdf http://themonadreader.files.wordpress.com/2011/10/issue19.pd...
- LunaSea 12y agoIt doesn't really matter how well the LISP version was implemented because in the end people will choose the language with modern libraries and support. You can be as edgy as you want and use LISP but real-world scenarios take into account economical factors. And surprise, surprise no company gives a shit about the beauty of a solution.