Board Optimization - [DBTech] vB Optimise 2.0.1 (Lite)

vB Optimise Lite

The newly revamped vB Optimise was created for vBulletin 4, but has now been made compatible for vBulletin 3.8. In this release I have re-coded vB Optimise from the gound and focused stability over features, you'll notice Phrase Caching and vBAdvanced Integration have bit the dust, this is to maintain a sync state between this version and the vBulletin 4 release.

Professional version & feature list available @ www.DragonByte-Tech.com/forum
Priority support for Lite version is handled at the Developers Website.


What does it do?

vB Optimise is intended to optimise vBulletin software by integrating several PHP "cachers" and handling data before vBulletin. This works by encountering and handling data prior to vBulletin in order to skip the arbitary execution that would be more server intensive.

Real-Life Statistics

We've teamed up with some Big Forums to show you the impact of vB Optimise, you can view this public chart which shows both our statistics and theirs:

View Public vB Optimise Resource Statistics

Features

• Supported Extensions
  • APC
  • eAccelerator
  • Memcache
  • XCache
  • WinCache
  • Filecache
• Style Cacher
  Caches style data to globally reduce a query within all vBulletin forum-based pages.
• Template Cacher
  Caches template data to globally reduce a query within all vBulletin forum-based pages.
• Datastore Cacher
  Forces custom datastore items from modifications (including those from vB's blogs) to use your configured Datastore Cache method instead of being forced into the database. This reduces page queries by where affected.
• vB CMS Template Caching
  (Automatic) Corrects many uncached templates within vB CMS to reduce upto 20+ queries on CMS pages (number varies based on content).
• Optimal Settings Check
  Provides a quick interface to identify possible settings which can be changed on your forum for further optimisation.
• Self-System Tester
  Provides a relatively straight-forward system check to ensure your vB Optimise installation works fully.
• Automatic Cache Flusher
  Automatically flushes cache within the Admin CP based on specific triggers to make sure content does not remain stale on your forum.
• XCache Authentification
  Supports XCache Admin Authentification by allowing you specify the username/password in a configuration if needs be.

Features - Pro

• Notices Cacher
  Caches users dismissed notices to reduce a near-global query within all vBulletin forum-based pages.
• Showgroups Cacher
  Caches the showgroups query which becomes more intensive as your user-base grows.
• Forum Display Query Enhancement
  Enhances a stock vBulletin query within Forum Display to speed up the page.
• Forum Home WOL Cache
  Caches Forum Home "Who's Online" to remove an intensive query and allow larger sites to display this data without impact.
• vB Cache Override (Feature not available on vBulletin 3)
  Ability to override vBulletins new built-in database cacher for the CMS / Forum Sidebar Blocks to remove anything from 1 to 20+ queries based on your content.
• Full Guest Caching
  Ability to cache entire pages and serve them saving not only hundreds of queries but upto 90% of CPU processing towards Guests.
• Statistical Resource Savings
  Ability to see just exactly how many queries per day vB Optimise has saved your database. You'll be surprised at the numbers.
• Forum Resource Statistic
  Shows off vB Optimise resource saving statistics directly within forumhome statistics.
• ....and more!

Release Notes

If you've used vB Optimise before you'll be aware the previous version had phrase caching, however this caused complications with the way phrases are used within vBulletin so it has not been ported over at this time.


Available Translations
v1.6.0 French - Thanks to finereader

Change Log

[>>] Version 2.0.1
New launch for vB 3.8

[>>] Version 1.6.1
Automatic Cache Flusher has additional parameters to make sure no data is stale
Resolved Bug: Potential PHP error when using eAccelerator which cannot flush within Admin CP on certain actions

[>>] Version 1.6.0
New OpCode Cacher Support: WinCache

[>>] Version 1.5.0
Resolved Bug: Style cache may have fetched ID 0 instead of correct file
Resolved Bug: Filecache permissions may not have worked
Optimisation: Re-wrote some base code to enhance operations.

[>>] Version 1.0.1
Added XCache Authentification Support
Added Filecache Support

Support

Priority support will be handled at DBTech.

FAQ

Q: I have WinCache installed, but vB Optimise tells me it's not?
A: WinCache only introduced OpCode support in version 1.1, if you're using version 1.0.x you will need to upgrade.

Q: I'm using the XCache method, flushing doesn't work?
A: If you have XCache authentification, turn the admin option on within vB Optimise Settings, then edit ./vboptimise/config.php and specify your XCache username/password. Alternatively you can disable XCache authentification within php.ini:

xcache.admin.enable_auth = Off

Q: I have eAccelerator installed, but vB Optimise tells me it's not?
A: eAccelerator does not provide the caching extension by default, you will need to recompile PHP with additional flags. For more information read eAccelerator documentation located here: http://eaccelerator.net/wiki/CompileConfiguration (Specifically look at: with-eaccelerator-shared-memory)

[Chadi]

For sure I did. Eaccelerator is installed, loaded so is memcache/memcached.

root@server [~]# /usr/local/apache/bin/httpd -l
Compiled in modules:
core.c
mod_authn_file.c
mod_authn_default.c
mod_authz_host.c
mod_authz_groupfile.c
mod_authz_user.c
mod_authz_default.c
mod_auth_basic.c
mod_cache.c
mod_mem_cache.c
mod_include.c
mod_filter.c
mod_deflate.c
mod_log_config.c
mod_logio.c
mod_env.c
mod_expires.c
mod_headers.c
mod_unique_id.c
mod_setenvif.c
mod_proxy.c
mod_proxy_connect.c
mod_proxy_ftp.c
mod_proxy_http.c
mod_proxy_ajp.c
mod_proxy_balancer.c
mod_ssl.c
prefork.c
http_core.c
mod_mime.c
mod_status.c
mod_autoindex.c
mod_asis.c
mod_info.c
mod_suexec.c
mod_cgi.c
mod_negotiation.c
mod_dir.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_rewrite.c
mod_so.c


I get this if I enable memcache

Fatal error: Memcache is not installed in [path]/includes/class_datastore.php on line 186

// $config['Datastore']['class'] = 'vB_Datastore_Filecache';

// ******** DATASTORE PREFIX ******
// If you are using a PHP Caching system (APC, XCache, eAccelerator) with more
// than one set of forums installed on your host, you *may* need to use a prefix
// so that they do not try to use the same variable within the cache.
// This works in a similar manner to the database table prefix.
// $config['Datastore']['prefix'] = '';

// It is also necessary to specify the hostname or IP address and the port the server is listening on
/*
$config['Datastore']['class'] = 'vB_Datastore_Memcached';
$i = 0;
// First Server
$i++;
$config['Misc']['memcacheserver'][$i] = '127.0.0.1';
$config['Misc']['memcacheport'][$i] = 11211;
$config['Misc']['memcachepersistent'][$i] = true;
$config['Misc']['memcacheweight'][$i] = 1;
$config['Misc']['memcachetimeout'][$i] = 1;
$conf

I get the error if I uncomment the below and make it Memcached instead of Filecache

// $config['Datastore']['class'] = 'vB_Datastore_Filecache';

(line 141)


It has to be something with this mod because my modules are loaded and showing up in the outputs, phpinfo, processes.

[KevinL]

/*
$config['Datastore']['class'] = 'vB_Datastore_Memcached';
$i = 0;
// First Server
$i++;
$config['Misc']['memcacheserver'][$i] = '127.0.0.1';
$config['Misc']['memcacheport'][$i] = 11211;
$config['Misc']['memcachepersistent'][$i] = true;
$config['Misc']['memcacheweight'][$i] = 1;
$config['Misc']['memcachetimeout'][$i] = 1;
$conf

You have to remove the /* and \* from the section above...

[Chadi]

Thanks but still getting this error after uploading the config

Fatal error: Memcache is not installed in [path]/includes/class_datastore.php on line 186

With below config:

// $config['Datastore']['class'] = 'vB_Datastore_Filecache';

// ******** DATASTORE PREFIX ******
// If you are using a PHP Caching system (APC, XCache, eAccelerator) with more
// than one set of forums installed on your host, you *may* need to use a prefix
// so that they do not try to use the same variable within the cache.
// This works in a similar manner to the database table prefix.
// $config['Datastore']['prefix'] = '';

// It is also necessary to specify the hostname or IP address and the port the server is listening on

$config['Datastore']['class'] = 'vB_Datastore_Memcached';
$i = 0;
// First Server
$i++;
$config['Misc']['memcacheserver'][$i] = '127.0.0.1';
$config['Misc']['memcacheport'][$i] = 11211;
$config['Misc']['memcachepersistent'][$i] = true;
$config['Misc']['memcacheweight'][$i] = 1;
$config['Misc']['memcachetimeout'][$i] = 1;
$config['Misc']['memcacheretry_interval'][$i] = 15;

[KevinL]

And you're sure your memcache server is running? and you uncommented the second \* after that section you just copied there?

[Chadi]

Yes to both questions.

//$config['Datastore']['class'] = 'vB_Datastore_Memcached';

    // ******** DATASTORE PREFIX ******
    // If you are using a PHP Caching system (APC, XCache, eAccelerator) with more
    // than one set of forums installed on your host, you *may* need to use a prefix
    // so that they do not try to use the same variable within the cache.
    // This works in a similar manner to the database table prefix.
// $config['Datastore']['prefix'] = '';

    // It is also necessary to specify the hostname or IP address and the port the server is listening on

$config['Datastore']['class'] = 'vB_Datastore_Memcached';
$i = 0;
// First Server
$i++;
$config['Misc']['memcacheserver'][$i]        = '127.0.0.1';
$config['Misc']['memcacheport'][$i]            = 11211;
$config['Misc']['memcachepersistent'][$i]    = true;
$config['Misc']['memcacheweight'][$i]        = 1;
$config['Misc']['memcachetimeout'][$i]        = 1;
$config['Misc']['memcacheretry_interval'][$i] = 15;

// ****** The following options are only needed in special cases ******

    //    ****** MySQLI OPTIONS *****

root@server [~]# ps aux | grep memcache
root      6140  0.0  0.0  5316  736 pts/0    S+   18:22   0:00 grep memcache
nobody   27945  0.0  0.0  2896  836 ?        Ss   16:06   0:00 /usr/local/bin/memcached -u nobody -d -m 2048 -l 127.0.0.1 -p 11211


root@server [~]# ps aux | grep memcached
root      6150  0.0  0.0  4156  736 pts/0    S+   18:22   0:00 grep memcached
nobody   27945  0.0  0.0  2896  836 ?        Ss   16:06   0:00 /usr/local/bin/memcached -u nobody -d -m 2048 -l 127.0.0.1 -p 11211

[KevinL]

hmmm weird. The only other thing I can think of is...do you have memcache installed with memcached server? I'm sure you do...just a thought though.

These are two good write ups...

http://www.vbulletin.com/forum/showp...4&postcount=39

http://pastebin.com/m695d4b5b

[Chadi]

That vb.com guide is what I already used. I already pasted earlier the output to show memcached is running. I installed all 3: libevent, memcache, memcached and recompiled apache via Easy apache, restarted httpd before/after, etc.

root@server [~]# php -i | grep -i 'memcache'
OLDPWD => /root/memcache-3.0.2
_SERVER["OLDPWD"] => /root/memcache-3.0.2
_ENV["OLDPWD"] => /root/memcache-3.0.2

root@server [~]# ps aux | grep memcached
root      4823  0.0  0.0  5024  736 pts/0    S+   20:55   0:00 grep memcached
nobody   27945  0.0  0.0  2896  836 ?        Ss   16:06   0:00 /usr/local/bin/memcached -u nobody -d -m 2048 -l 127.0.0.1 -p 11211

[Chadi]

Ok got it. I had to remove the entire path to memcache.so (from php.in file) and just leave it as memcache.so

I enabled memcache in the vboptimize module successfully.

However, two things:

noticed no speed difference
this monitoring tool shows no difference (even on refresh)
http://livebookmark.net/journal/2008...s-like-apcphp/

[KevinL]

That last one is all I had haha sorry. Wish I could do more. That really would have been what I thought it would have been when I looked at it again. It was saying that memcache is not installed....maybe ask your host to check it out for you and make sure?

[KevinL]

In all honesty I have found that xcache seemed faster them memcache for this.