4 ms·
>Why would you even change your server if a new one came out? Woo is many times faster than Hunchentoot. And projects can die. >a person needs to understand t
by eudox 11y ago
>Why would you even change your server if a new one came out?
Woo is many times faster than Hunchentoot. And projects can die.
>a person needs to understand the problem a tool solves before using the tool; otherwise you're training a code monkey, not a programmer.
There's a reason we use high-level languages: They hide irrelevant details. You shouldn't have to learn how TCP works or know every detail of HTTP to know what can be done with it.
- deleted 11y ago[deleted]
- lispm 11y ago> Woo is many times faster than Hunchentoot. "Hello World" on the local machine... https://github.com/fukamachi/woo/blob/master/benchmark.md https://github.com/fukamachi/woo/blob/master/benchmark.md is that what you mean by 'faster'? Personally I'd prefer a more representative benchmark, which actually uses the network... Really measuring the qualities of a Web server is a bit more work.
- eudox 11y ago>is that what you mean by 'faster'? Yes.
- e12e 11y agoSo, for multi-threaded, it's within a factor of 2. That's not bad. I wonder how much of that is likely to be eaten up in a real-world application. Interesting that woo is so much more performant for the single-threaded case though. But it hardly matters as both support multi-threaded, and both are much faster with multiple threads...