distributed APC on each of the servers, if I am not wrong ...

but I think there is currently no way to test this, as the site is productive and any problem would not be good ;)

Maybe later we can install a distributed test-environment.



One more wish:
include active support for TMS (by Andreas), meaning everytime a template-edit is done, your cache should be flushed

Installed on 3.7.3 using memcache and it's working with no problems. The board does appear to be running faster/smoother.

Well I'm not positive about APC, but I know distributed Memcache wouldn't be an issue because Memcache handles all the distribution, hopefully APC does the same thing.

If you'd like Zeropage, I could make a modification for you which will only activate vB Optimise for your user on your forum, that way any error that does occur will only be seen by you :)

Deceptor, as this site is from a customer of mine, I will ask first. I will get back on you if they are interested :)


I am now using your 1.1.0 on another site (one server, normal) and activated it using APC. Should the setting in vB's config.php still beor would this "double" the caching into the APC if your AddOn is active, too ?

It would not double the cache with APC on vBulletin and vB Optimise. vBulletin will only use that for the datastore, what vB Optimise takes care of is different. I personally use Memcache for the vBulletin Datastore and vB Optimise with no issues :)

There was an issue with eAccelerator when that cache was full (eg. new items could not be inserted and those old values were loaded), but it has been fixed since 3.6.something were the logic was changed (items are now being deleted from cache when they need to be updated, so in worst case they are being loaded from db if the case is full).

Glad to hear it, I saw vBulletin has since put the eAccelerator class back in as normal so I figured it'd be safe :)

Thanks for the information.

btw I am running this on 3.7.4PL1 without any problem :)

Yeah this is mint :)

One more question deceptor,

I am using Filecache, with NO suphp.

My server undergoes a check every 24 hrs to identify any php files that are chmod 0777. If they find any, they are automatically set to 0644.

Can this cause some problem? Does vboptimise attempt to write to already created php files?

Thanks