Unixy.net Cpanel Varnish Plugin 1.4.4b released

Unixy.net Cpanel Varnish Plugin 1.4.4b has been released.

Change log:

  • Performance improvements and less long-term hoggin of memory
  • template configurations to choose from in “templates/” directory
  • Ability to control static files TTL via WHM
  • Various minor bug fixes

Looks like you can now choose from several preset Varnish startup configuration templates from small, medium, large, huge and failsafe.  The default static file TTL also seems to have been reduced from 120 minutes to 20 minutes – guess now that you can change this value in WHM Varnish admin area, it doesn’t matter as much. I’ve already made the suggestion that an additional Varnish startup option be added for httpd_headers as default Varnish value I think is 64, I’ve raised mine to 384 to reduce number of Http Error 503 messages that may occur. Tried raising to 512 but sites wouldn’t load even if Varnish restarted properly ? If anyone have any ideas why, please reply to this article 🙂

Some of the preset Varnish startup configuration choices in Unixy.net Cpanel Varnish Plugin 1.4.4b.

Small preset with 32MB memory assigned, min and max threads at 40 and 200

DAEMON_OPTS="-a :80 -T localhost:6082 -p thread_pools=2 -p thread_pool_min=40 -p thread_pool_max=200 -p thread_pool_add_delay=2 -p sess_workspace=32768  -f /etc/varnish/default.vcl -u varnish -g varnish -s file,/home/varnish/varnish.bin,32M"

Medium preset with 128MB memory assigned, min and max threads at 100 and 900

DAEMON_OPTS="-a :80 -T localhost:6082 -p thread_pools=2 -p thread_pool_min=100 -p thread_pool_max=900 -p thread_pool_add_delay=2 -p sess_workspace=32768  -f /etc/varnish/default.vcl -u varnish -g varnish -s file,/home/varnish/varnish.bin,128M"

Large preset with 1024MB memory assigned, min and max threads at 150 and 1500 and bumped thread_pools from default 2 to 3

DAEMON_OPTS="-a :80 -T localhost:6082 -p thread_pools=3 -p thread_pool_min=150 -p thread_pool_max=1500 -p thread_pool_add_delay=2 -p sess_workspace=32768  -f /etc/varnish/default.vcl -u varnish -g varnish -s file,/home/varnish/varnish.bin,1G"

Huge preset with 2560MB memory assigned, min and max threads at 00 and 3000 and bumped thread_pools from default 2 to 4. Wait a minute – typo I guess so already notified Unixy.net and 3000. Update: Has been fixed the intended value for thread_pool_min = 300. So if you already downloaded 1.4.4b, either re-download it or make the change manually.

DAEMON_OPTS="-a :80 -T localhost:6082 -p thread_pools=4 -p thread_pool_min=300 -p thread_pool_max=3000 -p thread_pool_add_delay=2 -p sess_workspace=32768  -f /etc/varnish/default.vcl -u varnish -g varnish -s file,/home/varnish/varnish.bin,2.5G"

Failsafe preset with 16MB memory assigned, min and max threads at 50 and 100

DAEMON_OPTS="-a :80 -T localhost:6082 -p thread_pools=2 -p thread_pool_min=50 -p thread_pool_max=100 -p thread_pool_add_delay=2 -p sess_workspace=32768  -f /etc/varnish/default.vcl -u varnish -g varnish -s file,/home/varnish/varnish.bin,16M"

Time permitting, will upgrade from 1.4.2b and test 1.4.4b out.


Previous:
Next:



MaxCDN Site Acceleration

Get Cost Effective Content Delivery
Unbeatable speed, stats, & price
http://www.maxcdn.com



2 Comments

  1. Hi George, congratulations on your blog and excellent work for years.

    I have a question about this article, is the cpanel varnish plugin 1.4.4b compatible with article vB4Mance Part 5 …?

    http://www.vbulletin.com/forum/entry.php/2440-vB4Mance-Part-5-Expert-Level-Boosting-vBulletin-Performance-with-Advanced-Caching

  2. Thanks r.goz

    Unixy.net Varnish cpanel plugin operates differently form usual standalone default Varnish as explained in my article at http://vbtechsupport.com/33/. So you don’t need Mike’s Varnish boost plugin listed at http://www.vbulletin.com/forum/entry.php/2440-vB4Mance-Part-5-Expert-Level-Boosting-vBulletin-Performance-with-Advanced-Caching when using Unixy.net Varnish cpanel plugin. Just a note Unixy.net Varnish cpanel or standalone Varnish usage with vB 3.8.x works fine, but I found with vB 4.1.2 might need a change in 2 vB files to set the backend port your use for Apache or Litespeed when Varnish sits in front – read http://vbtechsupport.com/290/ for full details.

Leave a Comment