The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
![]() |
|||||||||||||||||||||||||||
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
Features - Pro
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: Code:
xcache.admin.enable_auth = Off 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) Download Now
Show Your Support
|
Comments |
#1152
|
||||
|
||||
![]()
I'm using VBSEO 3.x, Can I use VB Optimise ????????
And ... How do I know that I should use "Memcache" or "Filecache" ????? |
#1153
|
||||
|
||||
![]()
vB Optimise is compatible with vBSEO, if there are any issues let me know
![]() As for cachers, everyone can use "Filecache" (that's the most basic), as for Memcache/XCache/etc.., if unsure contact your host, generally these are not pre-installed so you may need one installing (I recommend XCache for typical setups). |
#1154
|
|||
|
|||
![]() ![]() Can you help me? My xcache.ini Code:
[xcache-common] ;; install as zend extension (recommended), normally "$extension_dir/xcache.so" ;zend_extension = /usr/lib/php/modules/xcache.so ; zend_extension_ts = /usr/local/lib/php/extensions/non-debug-zts-xxx/xcache.so ;; For windows users, replace xcache.so with php_xcache.dll zend_extension_ts = c:/php/extensions/php_xcache.dll ;; or install as extension, make sure your extension_dir setting is correct ; extension = xcache.so ;; or win32: ; extension = php_xcache.dll [xcache.admin] xcache.admin.user = "xxxxx" ; xcache.admin.pass = "qwerxxxx" xcache.admin.pass = "qwerxxxx" [xcache] ; ini only settings, all the values here is default unless explained ; select low level shm/allocator scheme implemenation xcache.shm_scheme = "mmap" ; to disable: xcache.size=0 ; to enable : xcache.size=64M etc (any size > 0) and your system mmap allows xcache.size = 32M ; set to cpu count (cat /proc/cpuinfo |grep -c processor) xcache.count = 4 ; just a hash hints, you can always store count(items) > slots xcache.slots = 8K ; ttl of the cache item, 0=forever xcache.ttl = 0 ; interval of gc scanning expired items, 0=no scan, other values is in seconds xcache.gc_interval = 0 ; same as aboves but for variable cache xcache.var_size = 32M xcache.var_count = 1 xcache.var_slots = 8K ; default ttl xcache.var_ttl = 0 xcache.var_maxttl = 0 xcache.var_gc_interval = 300 xcache.test = Off ; N/A for /dev/zero xcache.readonly_protection = On ; for *nix, xcache.mmap_path is a file path, not directory. ; Use something like "/tmp/xcache" if you want to turn on ReadonlyProtection ; 2 group of php won't share the same /tmp/xcache ; for win32, xcache.mmap_path=anonymous map name, not file path xcache.mmap_path = "/tmp/xcache" ; leave it blank(disabled) or "/tmp/phpcore/" ; make sure it's writable by php (without checking open_basedir) xcache.coredump_directory = "" ; per request settings xcache.cacher = On xcache.stat = On xcache.optimizer = On [xcache.coverager] ; per request settings ; enable coverage data collecting for xcache.coveragedump_directory and xcache_coverager_start/stop/get/clean() functions (will hurt executing performance) xcache.coverager = On ; ini only settings ; make sure it's readable (care open_basedir) by coverage viewer script ; requires xcache.coverager=On xcache.coveragedump_directory = "" |
#1155
|
|||
|
|||
![]()
I would assume you're running a windows server from the location you have set up for your xcache dll (plus dlls are windows only). Koloxo is a control panel so doesn't tell us if you're running apache or not. However I would guess your problem is here:
xcache.mmap_path = "/tmp/xcache" that's a linux filepath - fix it and restart whatever you use if it isn't apache and try again ![]() If that doesn't help I would suggest going to the xcache site for support as this is certainly an xcache issue not a vbulletin/vboptimse issue |
#1156
|
||||
|
||||
![]()
Pretty much what rsj1 said - XCache can commonly fail to "store" cache between sessions on setups which is one reason the System Test was created because outlining these issues is otherwise very had to visualise.
If changing the mmap_path or XCache support is able to resolve your setup issue it'd be great if you posted it here too incase others are experiencing the same issue ![]() |
#1157
|
|||
|
|||
![]()
I installed this on IIS and received the following error when I try to enable it:
vB Optimise: You have selected a cache method that vB Optimise has detected you cannot use, this may be because the extension required is either not installed or configured correctly on your server. Please contact your system administrator or hosting provider for more information. I am using Wincache and according to phpinfo it is enabled: wincache Opcode cache enabled File cache enabled Version 1.0.1325.0 Owner iisphp@microsoft.com Build Date Jan 21 2010 17:35:42 Any ideas what I might have missed? |
#1158
|
||||
|
||||
![]()
Trana - WinCache added var cache support in 1.1, you're using 1.0 (however note WinCache 1.1 is in beta). This is covered in the FP FAQ:
Quote:
|
#1159
|
|||
|
|||
![]()
Fantastic product, thanks so much!
|
#1160
|
|||
|
|||
![]()
I've gotten my host to enable eAccelerator but now when I try to flush the cache I get this error.
vB Optimise: Your eAccelerator requires you to specify permission to this directory to allow vB Optimise to clear your cache. For more information please visit here. |
#1161
|
||||
|
||||
![]()
Hi nascartr,
eAccelerator can be configured with protection, as such it requires you to manually give scripts permissions to access certain functions (in our case the flush). You or your host will need to edit your php configuration for eAccelerator and specify the location to: /your/path/to/forums/vboptimise/core/core_vboptimise.php within the setting eaccelerator.admin_allowed_path. Seems silly I know, but that's eAccelerator for you ![]() |
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|