Return-Path: 
 <dev-return-10063-apmail-lenya-dev-archive=lenya.apache.org@lenya.apache.org>
Delivered-To: apmail-lenya-dev-archive@www.apache.org
Received: (qmail 4714 invoked from network); 8 Apr 2005 11:16:38 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 8 Apr 2005 11:16:38 -0000
Received: (qmail 695 invoked by uid 500); 8 Apr 2005 11:16:37 -0000
Delivered-To: apmail-lenya-dev-archive@lenya.apache.org
Received: (qmail 655 invoked by uid 500); 8 Apr 2005 11:16:37 -0000
Mailing-List: contact dev-help@lenya.apache.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Post: <mailto:dev@lenya.apache.org>
List-Help: <mailto:dev-help@lenya.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@lenya.apache.org>
List-Subscribe: <mailto:dev-subscribe@lenya.apache.org>
Reply-To: "Lenya Developers List" <dev@lenya.apache.org>
Delivered-To: mailing list dev@lenya.apache.org
Received: (qmail 641 invoked by uid 99); 8 Apr 2005 11:16:37 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from idmailgate2.unizh.ch (HELO idmailgate2.unizh.ch)
 (130.60.68.106)
  by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 08 Apr 2005 04:16:36 -0700
Received: from zisp0103.unizh.ch (zisp0103.unizh.ch [130.60.7.143])
	by idmailgate2.unizh.ch (8.12.10/8.12.10/Debian-2) with ESMTP id
 j38BGSvo004329
	for <dev@lenya.apache.org>; Fri, 8 Apr 2005 13:16:30 +0200
Date: Fri, 8 Apr 2005 13:16:28 +0200 (MEST)
From: Jann Forrer <jann.forrer@id.unizh.ch>
X-X-Sender: forrer@zisp0103.unizh.ch
To: Lenya Developers List <dev@lenya.apache.org>
Subject: Re: DO NOT REPLY [Bug 32840]  -    replace sitetree script with one
 based on XMLHTTP
In-Reply-To: <1112951250.21365.32.camel@localhost.localdomain>
Message-ID: <Pine.A41.4.58.0504081257260.20148@zisp0103.unizh.ch>
References: <200503232126.j2NLQ4Rs000558@ajax.apache.org>
  <42429735.2000401@wyona.com>
  <Pine.A41.4.58.0503241213460.20420@zisp0303.unizh.ch>
 <1111668630.17205.30.camel@localhost.localdomain>
 <Pine.A41.4.58.0503241400110.25966@zisp0303.unizh.ch>
 <Pine.A41.4.58.0504071303420.22690@zisp0203.unizh.ch>
 <1112877288.21365.19.camel@localhost.localdomain>
  <42555399.2060402@wyona.com>
 <1112951250.21365.32.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On Fri, 8 Apr 2005, Josias Thoeny wrote:

> <snip/>
>
> > Before, the sitetree was generated from the sitetree.xml file.
> > But now, the SiteTreeGenerator uses the SiteTree object, currently
> > a DefaultSiteTree, which holds the sitetree in a DOM.
> >
> > Generating the sitetree from the DOM means heavy load on the DOM
> > itself and since the getLabels() method of SiteTreeNodeImpl access
> > the DOM in an asynchronous manner, it is  most likely that the DOM
> > get corrupted (bug 33908).
>

I did apply the changes proposed by Felix in bug 34348 and I get rid of
the error messages and the disorganization of the sitetree due to above
mentioned problems :-) (which did occur when i put heavy load on a lenya
live site). Now I got zero error messages and the sitetree keeps in good
order :-)

> Concerning the performance, something else just came to my mind:
> It might make sense for the SiteTreeGenerator to implement the
> CacheableProcessingComponent interface. That way, its output could be
> cached by cocoon, which should increase the performance.
> The problem is how to know whether a cached result is still valid (i.e.
> how to implement the SourceValidity).
> Anyway, some profiling might be useful to see if this is really an
> issue.
>

As alread mentioned I did some load testing using JMeter. The Results are
probably of interest. I test a lenya live site access it directy via
servlet engine (tomcat) and the same site static exported (wget) access it
via apache.

My Computer:
linux           : Linux version 2.6.8 (SuSE 9.2)
model name      : Intel(R) Pentium(R) 4 CPU 3.20GHz
cache size      : 1024 KB

Testplan:
50 concurrent user access 10 times 2 pages (1000 Request)

Results (summarized):

Tomcat: 1.5 request / second
Apache: 100 request / sedond

There is certainly room to enhance the lenya/tomcat performance. Some
possibilites have already been discussed on this lis e.g.
mod_lenya, simple caching mechanism (as described by Michi Wechner some
times ago), using apache to access images ......

Jann

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org