Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 12342 invoked by uid 500); 10 Dec 2002 12:47:01 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 12327 invoked from network); 10 Dec 2002 12:47:00 -0000 Date: Tue, 10 Dec 2002 12:47:00 +0000 Subject: Re: Cocoon performance tuning Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) From: Stuart Roebuck To: cocoon-dev@xml.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: <3DF5D0E3.9090102@outerthought.org> Message-Id: <79A3C2BC-0C3D-11D7-9557-0030655555CE@adolos.co.uk> X-Mailer: Apple Mail (2.551) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tuesday, December 10, 2002, at 11:32 am, Steven Noels wrote: > Konstantin Piroumian wrote: > >> What about predefined configuration modes: development and >> production? This >> can be done using two separate config file sets and be switched using >> a -D >> startup option or an application init parameter. > > Beats me ATM - if you can provide me with some more hints, I could do > it that way for 2.1/HEAD. > > I will hardcode it in the 2.0.4 branch, however - maybe we can do a > silent re-release then? I have moved over to using 2.0.4 and have hit a number of issues with the release. If there is a (relatively) 'silent' re-release then I think there are a number of performance related issues that would be worth including. Particularly given that that this fundamentally *the* Cocoon release at the moment. I'm still checking things a little before I raise the issues, but so far my two points are: 1. Bug ID 12915 and the work-around in 2.0.4 mean that static image files are not cached by browsers, leading to significant performance issues compared with 2.0.3. see: 2. In 2.0.3 (or thereabouts!) we used to get lots of ERROR level errors with broken pipes when users disconnected before fully receiving a response. This was a problem in itself. In 2.0.4 these same errors appears to be labelled FATAL. I need to do some further checking here to make sure this isn't a failure of our own code, but initial examination would indicate that it isn't. Stuart. Public Key - 1024D/88DD65AF 2001-11-23 Stuart Roebuck (Adolos) Key fingerprint = 89D9 E405 F8B1 9B22 0FA2 F2C1 9E57 5AB1 88DD 65AF ------------------------------------------------------------------------ - Stuart Roebuck stuart.roebuck@adolos.com Systems Architect Java, XML, MacOS X, XP, etc. ADOLOS --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org