Michael Homeijer wrote: > A quote from a report about the migration: > "The expected performance improvement was not confirmed by the obtained > results. Performance of the c2 site was dramatically lower than of the c1 > site. In 10 minutes, the c1 site was able to process 16283 catalogue > requests and send out 6MB of pages, the c2 site managed 1011 requests and > 400 kB."
We have same problemes here. Cocoon1 is very slow, but stable. We are no more working with it because of the lack of sitemap (sitemap is a great idea). C2 is using amazing quantity of memory, go to the status page, each time you reload it, C2 is using about 1 Mbytes of memory (a <map:read /> for image, and a <map:generate type="status"/>, <map:transform type="xslt"/> and <map:serialize type="html"/>). Reloading a page like documents/developing/avalon.html is costing something like 9 Mbytes. Under heavy load, we have stability problems. Sometimes, connection are accepted, but nothing is going out of the pipe (TidyGenerator reading files, XMLSerialiser, 10000+ files). Servlet threads are exhausted and we have to restart C2. Most of the time, error reporting is not helpful. Despite this, do not misunderstand me, C2 is great, I put it everywhere. -- Sébastien Koechlin - IVision - [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
