While I was throwing away from bogus data-copy operations from the mod-proxy-core code I stumbled over a simple question:
Why do we copy the HTTP response data from the backends at all ?
We are just forwarding them in most cases without touching them.
Some time ago we got a request on how to implement COMET with lighttpd. I responded with a idea about a mod_multiplex which would allow the let the client open a COMET-channel and give the backend the possibility to feed multiple channels at once with the client to poll for new data.
Basicly it would separate the HTTP Request-Response cycle from the underlying connection. HTTP would be used to open the connection and reopen it in case it went away, but otherwise it would be just a data-channel for your JavaScript/AJAX content we want to send to the client when WE (the content-provider) want.
Thanks to brave testers in #lighttpd the AIO-support is stabilizing very well and the corruptions that have been reported are fixed now.
Next to bugfixes, I implemented chunk-stealing and doubled the performance of aio for small files (100k) [16MByte/s instead of 9MByte/s].
Download: www.lighttpd.net/download/lighttpd-1.5.0-r1454.tar.gz
Yeah, really.
Before you jump around and empty a barrel of beer, try to compile it first. :)
Download: www.lighttpd.net/download/lighttpd-1.5.0-r1435.tar.gz
mod-proxy-core has 3 different balancers for different needs. Round Robin, Shortest Queue First and CARP.
The benchmarks only showed results for small files (100kbyte). Time to add larger files to the pool and talk about the chunk-size.
1.5.0 will be a big win for all users. It will be more flexible in the handling and will have huge improvement for static files thanks to async io.
The following benchmarks shows a increase of 80% for the new linux-aio-sendfile backend compared the classic linux-sendfile one.
trunk/ just got support Linux Native AIO.
You might wonder why it takes to long to release 1.5.0 when most of it is already in trunk.
At MySQL we are in the final strokes of getting a GA release of Monitoring and Advisoring Service of MySQL Enterprise out of the door.
I’m still monitoring the IRC channel, but all development time is going into my MySQL stuff right now.
Only 2 weeks after .12 hit the servers we have a new release cleaning up
the issues that were introduced by it.
On the fix side we have:
New are
Debian user have to compile their lua-support with:
$ configure —with-lua=lua5.1 …
Enjoy this release and watch out for 1.5.0 on the horizon. :)
Download