Hi, This is some additional information on the complexity of our site and the machines we used to compare C1 and C2.
Both sites were installed on one Sun E250, 1x400MHz uSparcII, 512 MB,
2x18GB. Installed software was iPlanet Enterprise server 4.1sp9 (2
instances, both on port 80; only one instances was activated at a time);
Borland Application Server 4.5.1 and Oracle Enterprise Server 8.1.7.
Cocoon versions: Cocoon 1.8.2 ("Cocoon 1") and Cocoon 2.0 final release
("Cocoon 2").
The java virtual machine used was Java Development Kit JDK 1.3.1b24, virtual
machine flags '-servervm -Xms100000000 -Xmx200000000' (iPlanet servlet
engine) and '-servervm -Xms50000000 -Xmx100000000' (BAS ejbcontainer).
Oracle init parameter settings were the standard "small" database parameter
settings.
Our site uses authorisation on menu items on a per user/role basis,
personalisation on a per company basis and localization on a per
country/language basis. This results in a very dynamic site with very
complex pipelines (see attachment). Personaly I think the requirements for
this site are one the edge of what I would recommend to implement with
Cocoon right now.
I'd recommend Cocoon 2 for any project less complex, because with little
effort you are able to influence the performance of the site (if you know
what to look for) and the programming model is great. I would just help if
Cocoon (probably XSP?) scaled a little better, because at this moment it
takes too much effort and not using XSP would mean building around 50
generators for the site we built. (Still don't know if XSP is the problem,
because the project is waiting for new resources right now :-( ).
Michael Homeijer
-----Original Message-----
From: Michael Homeijer
Sent: woensdag 2 januari 2002 11:03
To: '[EMAIL PROTECTED]'
Subject: Cocoon scalability continued
pipeline.gif
Description: GIF image
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
