Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Subject: benchmark website build (Was: Forrest 0.5 outstanding issues)
From: David Crossley <crossley@indexgeo.com.au>
To: forrest-dev@xml.apache.org
In-Reply-To: <3EEF8E51.30803@che-che.com>
References: <3EE8320E.2010601@apache.org>
	 <20030614104743.GE2758@expresso.localdomain> <3EEB35A1.8020202@apache.org>
	 <20030615042317.GA1127@expresso.localdomain> <3EEC96D1.60203@apache.org>
	 <20030616094852.GB617@expresso.localdomain> <3EED95B7.200@apache.org>
	 <20030616112204.GN617@expresso.localdomain> <3EEDD097.2050302@apache.org>
	 <3EEDE444.7010602@che-che.com> <20030617130839.GF3286@expresso.localdomain>
	 <3EEF8E51.30803@che-che.com>
Content-Type: text/plain
Organization: 
Message-Id: <1056091208.1704.324.camel@ighp>
Mime-Version: 1.0
Date: 20 Jun 2003 16:40:09 +1000
Content-Transfer-Encoding: 7bit

We already have a website in Forrest CVS that could perhaps be used for
this. The src/resources/fresh-site is the stuff that creates a new
project when you do 'forrest seed'. This also currently gets built by
Forrestbot. So if we make a few enhancements as Cheche suggests, then
this site could remain unchanged and be used for testing.
http://forrestbot.cocoondev.org/site/xml-forrest-template

Surely it would not be hard for "forrestbot" to append timing info into
a log file.

--David

Juan Jose Pablos wrote:
> Jeff Turner wrote:
> >Juan Jose Pablos wrote:
> >>Nicola Ken wrote:
> > 
> > ...
> > 
> >>>I don't know if/when I'll have time, but I'll surely want to work on this.
> >>>
> >>>We could also define a test site that gets generated every night and 
> >>>shows us if/how performance is affected. I can use my server here to do 
> >>>it since at night it doesn't do anything else, all I need is a test 
> >>>site. What about taking our site now, freezing it, and checking it in a 
> >>>test dir, so it remains as the base of the tests? Or IYHO is there a 
> >>>better real-life test site we could use?
> >>>
> >>
> >>I like that, can we just create a test site with test cases?, in this 
> >>way, we make sure that things still working.
> > 
> > We'd just need to log times for the sites on
> > http://forrestbot.cocoondev.org/.
> > 
> > --Jeff
> 
> We can not compare that, because:
> 
> What about if you add/remove more pages?
> What about if you modify the skin with less/more features?
> 
> If you want to test the performance on time, then you have to create 
> test cases that does not change that much.
> I got a feew examples ( please add more):
> 
>   table of 50 elements.
>   render a svg logo
>   Display a page with the maximum amount of elements posible for these 
> diferent source formats:
> 
>    docv12 -> html
>    docbook-> html
>    wiki -> html
>    faq -> html
>    howto -> html
>    rss -> html
> 
> and for a diferent output:
> 
>    docv12 -> pdf
> 
> 
> I can help on the creation of the pages, but I am not sure how to achive 
> the mesaure of that.
> 
> Cheers
> 
> Cheche