Will litespeed add support for async io or writeav? I heard these lower iowait when serving huge static files. This is the case on an inferior server running lighttpd, the iowait is much lower than on a higher end server running litespeed enterprise.
Async I/O make the kernel schedule tasks in a more orderly manner, so it leads to lower load, however, it does not mean it is faster. In most cases the server is disk bounded when async I/O benefits.
Today, I had to use my friend's server, running on lighttpd to serve the huge multimedia files because the iowait was really high and made my forum really slow. I was surprised that his server handled it fine with only 25% of my server's memory and load was well under 1. He said it's due to async io and I said why don't I suggest this to George.
When a server performance is disk bound, async I/O will help a lot, as normally disk operation will block the single thread server process.
We currently suggest a multi-CPU license for this kind situation.
To be fair, nginx does support multiple worker processes.
Great! i thought it does not
checked their wiki and find out thats awesome features! seems it has more stability with higher performances at least for statistic files toward lighty or maybe LS but PHP/RUBBY dynamic scripts
I've planned to port my major DL server with huge large files which pushes upto 600Mbit/s and 300Mbit avg to nginx and may do some benchmark stuffs to compare lighty, litespeed and nginx
async io & writeav setting
Linear Mode
