vBulletin's built in cache is doing a lot of the work.
How will the product work with the new features that were incorporated into versions since?
In 4.1.5, there have been XHTML, CSS, template, query, and function improvements. This is over 100 fixes of known bugs. This is a concern that vBOptimise may not be needed. Specifically there have been fixes for online.php and a number of other template cache issues using vBulletin's internal cache.
I never thought vBOptimise is bad, in fact, I just wrote an enormous reply, only to get timed out (forgot you guys don't have auto-save here yet)
VBSEO also has MaxCDN integration. Will you work to provide compatibility for both?
I like the idea of V3. What about people who use nginx/lighthttp or LiteSpeed? These use a pre-cache system. Does Optimise still have an effect?
The stated lack of compatibility with 3rd party products is a concern. I often find myself integrating different products that are made freely available, purchased (hey -- VBOptimise is one of them), and of my own design. I even improve upon existing products when I can.
I am on the vBulletin testing team as well as VBSEO. This product occasionally stalls on my installation, whether with apache or LiteSpeed, and I think it may be due to compatibility problems with vBAdvanced, although I'm not sure. After some time of running the product, a white page is served up, either blank, or indicating that memcache utilized all available memory. This is unlikely NOT to be a bug, since I'm using a server with 24GB of DDR3 that has one big board on it.
I think you need to check out what is going on with the cache system that is pre-built into newer web servers that aim to replace apache. Does running vBOptimise under those conditions actually slow things down?
Overall I never meant to say it is a worthless product - however I remember a time where this thing saved my website when I had limited memory and resources. Administratively, my team is kind of creeped out to run it - since the white page issue made us come to a conclusion it either couldn't clear out the cache automatically, or something was wrong with a memory leak. Could be due to any component in the product, but who knows where. Under today's circumstances, with all options on, I am wondering if it would really save resources for my site. I am basically pre-caching my entire site into memory already with LiteSpeed. For most people running a basic board, this product will be great, however. I am running tons of mods and often times it is the goal of a publisher to make their site unique with both content and features. After all, vBulletin is an abundant system and used everywhere. Seeing stock vBulletins everywhere is kind of like seeing a million Facebook clones -- after awhile, some tinkering is needed.
I hope I have expressed my interest. I would never have written this, as it takes a lot of time to do so. I am constantly busy with other things, and I like the product so much that I wanted to bring this up. I hope you will look into further VBSEO cross-compatibility with the CDN feature in the next version, as well as universal support for the hooks system. This is your best product, as far as I am concerned. I was surprised to see a V3 in the works.