Yup, OSCache scales really nicely to even high-traffic sites. I have no complaints on that... JSPWiki is known to be used on sites which have grown from zero to 20,000 pages in two months, so I think it scales okay to these mid-sized tiers.
Note that JSPWiki caches things such as page content and the DOM tree (since 2.4). We don't cache the resulting HTML of all pages, because there are dynamic plugins which might change on every invocation of the page (such as the current time). However, the step from DOM to HTML is in general rather fast. /Janne On 6/6/06, Dave Johnson <[EMAIL PROTECTED]> wrote:
On 6/6/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > can someone comment on the ability for the Roller + JSPWiki pages > to be cached, which is a key performance and resource utilization > consideration? The integration between Roller and JSPWiki is lightweight and so you really have to consider them as separate applications. Roller has a highly configurable caching system and you can even plugin external caches like memcached if you want to, but I bet the out-of-the-box caching would work just fine. Roller is proven at high-traffic sites like blogs.sun.com, JRoller and IBM devWorks so I don't think it's performance is going to be an issue on the little Roller project site. JSPWiki uses OSCache for caching. I'm not sure it's been proven at high-traffic sites. Maybe Janne can comment on that? - Dave
