hIBEES, if vB Optimise is reporting an error then the method must not be available, it will test you have the functions available that are part of the method you selected, this works in the same way vBulletin does, does your vBulletin datastore run off of eAccelerator?
As for the profile bug, it has been fixed, the issue is caused by caching phrases with guests, the vBulletin session object goes its own root of querying phrases/languages for guests that currently I can't find a way to stop. This bug fix doesn't impact performance as caching phrases for guests still means the query is being ran, if anything it slightly helps by not attempting to cache phrases as they are continually called from the database when viewing as a guest.
This said, I can tell you my current forumhome statistics with the upcoming release of vB Optimise, this is a unmodified forum, with only vB Optimise installed:
As a member:
Quote:
Page Generation 0.03050 seconds, Memory Usage 924KB, Queries Executed 4
|
As a guest:
Quote:
Page Generation 0.02649 seconds, Memory Usage 860KB, Queries Executed 3
|
If you're wondering why my memory usage is so low, look into getting XCache installed on your server, at the time of fetching those results vB Optimise was using XCache too, along with vB Datacache using Memcache.
I'll have the new version out in the next couple of hours or so which will patch the issue and bring forward new features I explained in an earlier post