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)

[wolfstream]

Let's see here

Eaccelerator works. I've tested this and found it to be so. It's really easy to test if it works

Eaccelerator was compiled using THEIR recommended setup

YOUR setup doesn't detect eaccelerator functions. That's a problem in your setup. This needs to work with the eacc recommended settings, not the other way around.

There is definitely a problem here, as represented by at least two people. The problem is with how eaccelerator is configured. You shouldn't HAVE to reconfigure a server application for one plugin, in fact most people can not.

The recommended values for eaccelerator configuration (which, btw has worked for years without fail):

  ./configure \
  --enable-eaccelerator=shared \
  --with-php-config=$PHP_PREFIX/bin/php-config

Changes insisted by your code (and ONLY your code, btw):

  ./configure \
  --enable-eaccelerator=shared \
  --with-eaccelerator-shared-memory \ 
  --with-php-config=$PHP_PREFIX/bin/php-config

Again, this should be done properly, so that individuals DON'T have to recompile and reconfigure eacc, especially when they can't.

[Deceptor]

While I appreciate the feedback wolfstream, I think you're forgetting one vital thing here. Without the extension installed it is impossible for any php script to use eAccelerator functions, vB Optimise works exactly like vBulletin does for its datastore system for eAccelerator, and just about every other PHP script I've found that uses eAccelerator.

Please do not make claim there is a problem with the script when it was instead a problem with your eAccelerator setup. Ofcourse eAccelerator will work without the functions available in PHP, as it also works as a php optimiser in whole

[unp]

Even vbseo cache doesn't work with eaccelerator compiled without ' --with-eaccelerator-shared-memory \ ' , So there is no problem with vb optimse,

[Andreas]

@wolfstream
Incorrectly setting up eAccelerator is your fault - don't blame this script for a crippled eAccelerator installation.

[NolF]

Here are a list of options that affect performance and you might want to add to the "Optimal Settings Check"

Admin CP -> vBulletin Options -> Forum Display Options (forumdisplay) -> Show Users Browsing Forums

Admin CP -> vBulletin Options -> Thread Display Options -> Show Users Browsing Thread

Admin CP -> vBulletin Options -> Message Searching Options -> Automatic Similar Thread search

Admin CP -> vBulletin Options -> Thread Display Options (showthread) -> Check Thread Rating

Admin CP -> vBulletin Options -> Thread Display Options (showthread) -> Check Thread Subscription

Admin CP -> vBulletin Options -> Thread Display Options (showthread) -> Show Similar Threads?

There are some smaller ones such us

Admin CP -> vBulletin Options -> General Settings -> Use Forum Jump Menu

Admin CP -> vBulletin Options -> Cookies and HTTP Header Options -> GZIP HTML Output

Donated 10$ Not as much as lugicuk but 10$ you get

Great job the speed difference is astonishing ^^ the vba module is really a miracle ^^

Thanks

[Deceptor]

NolF - Thank you for your donation Regarding those options, most I've let out for now on purpose, regarding your first group of options, they come at expense of features, and it is my aim to be able to cache these, rather than drop them for performance, like I did with the forumhome WOL.

As for the other two, the forum drop down menu maybe something I cache too, and GZIP isn't always safe on all server setups, so I didn't put it in there because people would blame my script for telling them to use GZIP when it did damage it instead of good

But thank you for the suggestions, I'll probably concentrate on these areas in the next version

[wolfstream]

Without the extension installed it is impossible for any php script to use eAccelerator functions

That's so incorrect it's not even funny. Eaccelerator works FINE without the above compiled option. If it didn't, it would be put in the recommended settings.

I've had eaccelerator running for years. Cache? Right now, it's running at 30.30% (155.12MB/ 512.00MB), with the top script (right now) being accessed over 4k times since the last time it was cleared. There is no way you can NOT tell me eacc does not work properly, because it does.

Incorrectly setting up eAccelerator is your fault - don't blame this script for a crippled eAccelerator installation.

Again, wrong answer. If you don't know what you're talking about, please, don't try to step in and say you do. From their INSTALLATION GUIDE!

Step 1. Compiling eAccelerator

export PHP_PREFIX="/usr"

$PHP_PREFIX/bin/phpize

./configure \
--enable-eaccelerator=shared \
--with-php-config=$PHP_PREFIX/bin/php-config

make

You must specify the real prefix where PHP is installed in the "export"
command. It may be "/usr" "/usr/local", or something else.

Eaccelerator was not installed incorrectly at all. This product requires advanced setups and should be modified to work with the EA recommended settings. I've been installing EA the exact same way (eventually you just script it ) for clients for years, numerous clients, over a good 30+ servers. Have ANY of them complained about it 'not working'? Nope.

Again, using the above settings, EA has worked, and has cached scripts for years. Right now, I'm at about 5GB cache (should probably clean some of that up ), but it most definitely DOES work properly, using the recommended , out of the box, settings.

This is not a problem with anything but products trying to force users into an advanced EA compile.

[Deceptor]

As I said above wolfstream, eAccelerator will work at caching scripts because that's the main purpose of eAccelerator. But for PHP scripts to actually use eAccelerator functions it requires the extension. I've also said this is how vBulletin does things, and other scripts, a member above also pointed out vBSEO.

So unless you know a magic way for my script, vBulletin, vBSEO and anything else out there to use eAccelerator functions without the extension installed, please tell me, I'm always open to suggestions. Otherwise please stop making claim that there is something wrong with my script when clearly there isn't.

Regarding the eAccelerator recommended install, they don't expect most server setups to have scripts which use eAccelerator, and for the purpose of just caching php, it'll work.

[lolo?]

Hello i use the thanks mods the query in postbit or postbit legacy can be cached??
Sorry for this stupid question

[Andreas]

Originally Posted by wolfstream

That's so incorrect it's not even funny. Eaccelerator works FINE without the above compiled option. If it didn't, it would be put in the recommended settings.

http://bart.eaccelerator.net/doc/php...emory_php.html

It's clearly stated that you have to compile eAccelerator with support for shared memory if, well, you want to use shared memory!

There is no way you can NOT tell me eacc does not work properly, because it does.

To some extend it does: It caches PHP opcode.
But the content cache functions are non-working if not compiled like stated above.
Try to use eAccelerator as vBulletin datastore cache.

This is not a problem with anything but products trying to force users into an advanced EA compile.

If you call enabling a fature (that was on by default in eAccelerator < 0.9.5) "advanced" yes, it is.