Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 93978 invoked from network); 24 Mar 2004 12:42:52 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 24 Mar 2004 12:42:52 -0000 Received: (qmail 80231 invoked by uid 500); 24 Mar 2004 12:42:47 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 80171 invoked by uid 500); 24 Mar 2004 12:42:47 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 80155 invoked from network); 24 Mar 2004 12:42:46 -0000 Received: from unknown (HELO naomi.webworks.nl) (24.132.161.79) by daedalus.apache.org with SMTP; 24 Mar 2004 12:42:46 -0000 Received: from hippo.nl ([10.10.20.152]) by naomi.webworks.nl with Microsoft SMTPSVC(5.0.2195.6713); Wed, 24 Mar 2004 13:42:46 +0100 Message-ID: <40618246.5060308@hippo.nl> Date: Wed, 24 Mar 2004 13:42:46 +0100 From: Unico Hommes User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: documentation about performance and efficiency and caching References: <1080128762.1500.41228.camel@ighp> <40617D62.8050305@hippo.nl> <38150.10.0.0.5.1080131214.squirrel@ags01.agsoftware.dnsalias.com> In-Reply-To: <38150.10.0.0.5.1080131214.squirrel@ags01.agsoftware.dnsalias.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Mar 2004 12:42:46.0299 (UTC) FILETIME=[821246B0:01C4119D] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Antonio Gallardo wrote: >Unico Hommes dijo: > > >>Keep in mind that the caching system is currently in a state of flux >>given that we are trying to move away from Jisp. A lot of the >>alternatives manage the paging aspect that now involves the persistent >>store and store janitors themselves. >> >>A related observation: I consider the current Jisp version unuseable for >>any production site. The problem outlined here >>http://issues.apache.org/bugzilla/show_bug.cgi?id=26753 is very serious >>and has forced me to use the EHCache store for some of our clients >>instead (The only useable alternative besides perhaps JCS (haven't tried >>to use it yet) ATM). >> >> > >Good point Unico, BTW, what brakes us to make the change to JCS? It cannot >be worse than Jisp or yes? > >If a vote is needed to make JCS the default cache system, here is my +1. > > I personally don't have enough test data to justify such a move. As I previously noted there is a problem with page flushing during shutdown but this admittedly is a minor issue compared to the mentioned Jisp bug. Regarding performance testing I think Corin can provide more info on it than me. Alternatively we could go with EHCache as a default instead. I have been using it quite successfully for the last two weeks and the license issue has been cleared up as well. -- Unico