Presenting LiteSpeed’s Fast Huffman Encoder, our optimization tricks, and some benchmarks
One reason LiteSpeed outperforms nginx in HTTP/2 benchmarks is that LiteSpeed’s HPACK Huffman decoder is twice as fast as that used by nginx. Learn how our Huffman decoder works.
We have designed a flexible QUIC benchmarking program and included a testing script for easy test automation.
We teamed-up with Svend Gundestrup to generate a series of new scientifically-proven benchmarks using one of his Joomla sites in Denmark.
LiteSpeed Web Server is event-driven and Apache is process-based. A coffee shop analogy explains what that means and why you would prefer one over the other.
QCRAM-04 addresses the deadlock hazard, but is unable to minimize HoLB for a certain class of applications. Learn more.
One way to prevent attack is to not read from the stream until the decoder can process the stream immediately. This approach creates a deadlock hazard and is examined in this article.
Compression schemes that allow head-of-line blocking are targets for memory exhaustion attacks against the decoder. One way to avoid an attack is presented.
Head-of-line blocking causes priority inversion and vice versa. Learn more.