18
Please don't take this wrong. It's only meant as a matter of comparison..
2.0.13.2 Install, no hacks, default caching
============================================
Page Load Statistics: 0.686 Seconds | 105 Queries
2.2.3RC1 Install, no hacks, minimal caching
===========================================
Page Load Statistics: 0.407 Seconds | 46 Queries
*The 2.0.13.2 site only uses the caching that is used by default in XOOPS.
*The 2.2.3RC1 site has had minimal block/module caching tuning using the tools built into XOOPS.
*Both sites are on shared hosting accounts with over 500 websites on each server with no special optimizers other than Zend.
An optimization guide would be great, and there may even be a few things in there that the Core Devs could implement in XOOPS, but quite honestly, I'm not seeing a significant enough gain in performance to warrant a code fork.
When page load statistics are under 0.5 seconds with minimal caching, a difference of +/- 0.25 seconds is not that noticeable.
Now, granted, anything that can speed a site up is a good thing. That's why I think your optimization guide would be a handy tool. However, IMHO, instead of creating your own "version" of XOOPS, why not just work with the Core Devs on this?
Again, I'm just trying to clarify the differences here. No offense intended.
Best Regards,
James
Insanity can be defined as "doing the same thing over and over and expecting different results."
Stupidity is not a crime. Therefore, you are free to go.