[daisy] One Daisy wiki, many repositories?

[Kealy, John]

Oliver,

We are running 29 sites in one instance of the Daisy wiki and repository. We use apache as the front end and proxy jetty through various virtual hosts. 

I'd strongly recommend this approach as our me memory usage with that set up tends to be pretty small and we are running some sites that get a significant amount of traffic (~7,000 daily visits).

Best regards.

John Kealy

-----Original Message-----
From: daisy-bounces at lists.cocoondev.org [mailto:daisy-bounces at lists.cocoondev.org] On Behalf Of Olivier Lange
Sent: Wednesday, March 19, 2008 9:00 AM
To: daisy-users
Subject: [daisy] One Daisy wiki, many repositories?

Hi all,

Running side-by-side, I have 5 instances of Daisy (repo+wiki) on a Debian Linux server with 2GB of RAM.

When the wikis are under load, I noticed that the server started to swap memory and performance lowers for a while.

As adding RAM is not possible (hardware limit) and changing the hardware neither, I wonder if merging the Daisy Wikis into one single instance wouldn't lower memory consumption significantly?

I mean, provided Daisy powerful multi-site and skinning features, couldn't a single instance serve all sites, from different repositories?

The association between each site and it's repository should oviously be described (siteconf.xml?)

Does this make sense?

On the other hand, running distinct repositories instances is ok, as they consume less memory than the wiki, and they enforce separate document types, fields, users, roles and ACLs for each customer.

Just a wild guess: is it a matter of introducing new components within daisy.xconf for the distinct repositories, describing the binding between site and repository within siteconf.xml and having o.o.d.f.FrontEndContext figuring out what repository role to use, depending on the request?

Kind regards,
Olivier

--
Le Petit Atelier de Génie logiciel
t. +41-21-6487665, m. +41-76-5166212, http://www.petit-atelier.ch/