rc7 is out! We’ve upgraded to Varnish 3.0.2, fixed bugs, and made improvements to make your cPanel WHM server run even more faster than litespeed! Head out to the varnish download page: http://www.unixy.net/varnish

In brief:

• Upgrade Varnish to 3.0.2
• Increase httpd hdr len for req/resp
• Increase session WS
• Add Varnish monitoring crontab job

rc8 will see two neat features. The first will is a Slashdot Survive URL opt-in list where if you were to receive enormous traffic, Varnish can shield your server by responding directly to those requests (completely bypassing Apache or any server-side processing). So serving a slashdot-like audience will require a small fixed amount of memory as opposed to an unpredictable amount of resources (and most likely a server crash). The second feature will deal with aggressive bots. This addition creates a shared memory store for bots so they sources pages from the same store and prevent server crashes due to aggressive bots.

There’s more in 1.4.5rc8 so stay tuned!

Enjoy!

Litespeed users on cPanel WHM servers are realizing the benefits of running Varnish Cache in front of Litespeed to improve performance. While we (UNIXy) don’t officially provide support to subscribers running the cPanel Varnish Plugin with Litespeed, it does work with only a few extra manual steps. Keep in mind that we support this configuration for our fully managed VPS, dedicated server, and cluster clients. If you are a current client and need this configured, please open a ticket request.

In this post, I’m going to list the steps required to pair the cPanel Varnish Plugin with Litespeed on cPanel WHM servers. These few procedures apply to a blank cPanel installation (no Litespeed, no Varnish Plugin). The order below is important so don’t skip!

• 1. Configure your Apache / PHP with the desired options and extentions. Let EasyApache finish the build.
• 2. Install Litespeed using the command line installer with the port offset at 2000 (default).
• 3. From WHM -> Litespeed -> Build Matching PHP binaries. Let the Litespeed builder complete before proceeding.
• 4. Proceed with installing the cPanel Varnish Plugin. Let it complete.
• 5. Set the Litespeed Port offset to zero in Admin Console.
• 6. In Admin Console, Configuration -> Server -> General Settings -> Use Client IP in header -> Yes. Restart Litespeed.

About UNIXY

UNIXY is a long-time Varnish Cache user and evangelist. They have been offering Varnish acceleration to their clients for more than three years. They have released the first cPanel Varnish plugin as well as spun a new startup, Fastlayer, the on-demand HTTP accelerator for the cloud.

That’s all folks! I hope you find this useful.

The benchmarks are in! Find out how Apache smoked Litespeed with the help of Varnish: http://www.unixy.net/apache-vs-litespeed/

Cheers!

This error is not specific to Litespeed but can be encountered while building PHP with MySQL support on 64-bit systems. The fix is to tell the build that the MySQL client is indeed installed, but in a different directory, by adding the following flag to the configure line in Litespeed:

--with-libdir=lib64

The reason being the build doesn’t know at this point that it is dealing with a 64-bit OS. If adding the above switch does not work, be sure to install the MySQL client and libraries.

That’s all folks!

Update (2011-02-16): If you’re interested in running Varnish with cPanel, UNIXY has created a cPanel Varnish plugin. Our Varnish VCL configuration performs much better than Litespeed. Read more about it here: http://www.unixy.net/varnish

Update (2010-10-09): Should you be interested in a managed vBulletin dedicated server know that UNIXy has built a system that is ideal for those that want to run a lightening fast vBulletin forum. Visit the following product link:

https://www.unixy.net/secure/cart.php?a=add&pid=216

Varnish is an excellent Web accelerator that can be made to proxy requests in and out of a cluster of somewhat more fully fledged Web servers like Apache or Litespeed. It has some great features like its compiled language, called VCL, and C-like programming API.

Large vBulletin deployments tend to be heavy on CPU and memory due to PHP script processing. For a large vBulletin forum, we recommend a cluster of 5 physical servers with three of those running Xen virtualization. One of those servers will be dedicated to the MySQL master database. Three to be setup as “headless” PHP nodes and Varnish load balancing and failover. And finally one as the NFS file store. The three headless servers need to run Varnish in their own VM and Litespeed or Apache in their own VM similarly.

The varnish backend director functionality makes it ideal to balance incoming traffic across all PHP headless nodes. It makes the configuration scalable and plug and play especially when needing to scale out within hours. The challenge in this setup is in making Varnish work correctly with vBulletin. Otherwise, session problems will occur.

We have a lot to share on this implementation so keep checking this blog as we will post it all. In the next installment, we’ll go through our deployment of a large vBulletin forum for a customer. In the mean time, feel free to get in touch should you have a question or comment. If you are interested in us helping you accelerate your server, we have a page explaining the different technologies we deploy on our clients’ dedicated servers. Read up here: http://www.unixy.net/accelerate-your-server

Update: we are offering a Varnish configuration for vBulletin (3 & 4) for a one-time fee. We can also configure it free of charge should you decide to rent your fully managed dedicated server from UNIXY (http://www.unixy.net). Please contact us today to get your forum running with a blazing fast speed!

That’s all folks!