News for hackers. Stuff that matters.

A comment on A fast HTTP request/response parser for Common Lisp. Parent comment

Re:A fast HTTP request/response parser for Common Lisp by rgbrgb on Thursday October 30, 2014 @04:05PM (#8535488)
> (That outperforms Node!)

In what way? All of the benchmarks I'm seeing on that page indicate otherwise.

[ Parent | on HN ]
Re:A fast HTTP request/response parser for Common Lisp by eudox on Thursday October 30, 2014 @04:08PM (#8535510)
When he first posted it, it did, it looks like recent changes have brought that down:

https://github.com/fukamachi/woo/commit/be4a0db688af05ee204e...

[ Parent | on HN ]
Re:A fast HTTP request/response parser for Common Lisp by fukamachi on Thursday October 30, 2014 @04:13PM (#8535534)
Right. When I added default headers, the score went way down.

Probably libevent2 is the bottleneck and no way to make it faster without switching its backend (the cl-async's author is working on rewriting it with libuv now).

[ Parent | on HN ]
Re:A fast HTTP request/response parser for Common Lisp by aidenn0 on Friday October 31, 2014 @02:56AM (#8537617)
Out of curiosity did you try basic-binary-ipc? I would expect it would lose out to cl-async, but have never benchmarked the two against each other.
[ Parent | on HN ]
Re:A fast HTTP request/response parser for Common Lisp by thirsteh on Thursday October 30, 2014 @10:42PM (#8537054)
It would be quite surprising if it did, since Node's HTTP parser isn't Node/JavaScript, but highly optimized C.
[ Parent | on HN ]