Litespeed folks confirmed it was a memory leak in 4.0.19. They have patch fixed the leak and new 4.0.19 downloads will be memory leak free. Redoing the above test with 4.0.19 fixed version results in some improvements. Updated above table for re-run with fixed 4.0.19 version.
Looks like lower performance is due running out of connections in litespeed
default is 2000 max connections (left), raised connections (right)
![[IMG]](http://vbtechsupport.com/litespeed/benchmarks/jan28/runoutconnections_updated.png)
After raising litespeed max connection and max keep alive requests limit, litespeed cache really jumped into the lead with nearly 28k rps!
Updated table above.
Last edited: Jan 28, 2011