lighty's life

lighty developer blog

Thread Starvation

After getting covered with benchmark and stumbling over time-outs reported by http_load it was time to look a bit deeper into the problem. talks about how you can reduce the probability of time outs reported to the user. With the help of a new timing infrastructure you can now track the time spent a different stages of a request. With the help of gnuplot you can get a feeling of where the time is spent.

To make the long story short: If you use one of the async-io backends in 1.5.0 you want to set the server.max-read-threads to twice the number of disks.


Enable javascript to load comments.

Please note that we won't accept comments for posts older than 3 months! Also please use our bug tracker to report bugs, and our irc channel #lighttpd@freenode to chat.

« PRE-RELEASE: lighttpd-1.5.0-r1691.tar.gz lighttpd enters the Top5 »