Kryptronic Software Support Forum

There is too much of a mix of dynamic and static content on the pages to produce them statically.

One of the last pieces I want to do for V9 before it launches is a cache mechanism that caches portions of the skin and frequently accessed HTML pages and categories.  The spec I have now calls for caching different elements based on the browser's usergroup and mutlisite URL.  So basically each cached element would be cached based on site and user type.  By caching pieces of the output we save a lot of resources without sacrificing features and functionality.

This would be an on/off feature and wouldn't cause all the issues typical caches experience.  It's slated todo if time allows.  We're really trying to get this out the door ASAP as we've got quite a few clients waiting on upgrades already.

Submit a custom shop quote request if you'd like us to do an upgrade for you.  It's a custom shop job, and likely costs more than you think it will, due to the labor involved.  We can do anything from plain vanilla stock upgrades to porting over custom code.

Check what I posted about the proposed cache module in #3 above.

Caching will be available in V9 as per post 3 in this thread.  We're approaching it by balancing speed, resource usage and overall usability.  It's impossible to cache everything for everyone on an ecommerce site, however caching frequently hit page components works very well.  We're anticipating well over 75% of traffic will receive over 75% cached content in final pageviews based on traffic patterns, and what is cached.  That translates into speed and resource usage decreases without affecting usability at all.