One of the reasons is that XWiki SAS has almost all it's XWiki deployments using tomcat more by habit than anything else. I'm also not sure when we started that jetty was primetime.
It's true that XWiki works with the most lightweight servlet engines so jetty is probably as good as tomcat. Ludovic 2012/2/13 변형진 <kes...@kesarr.com> > I see that the performance using MySQL is better than using HSQL. > But why does XWiki recommend to use Tomcat as WAS? > > I have heard that Jetty is so efficient, lightweight and flexible that > it can replace Tomcat in many common cases. > So I'm playing with Nginx + configured XEM standalone package (Jetty + > MySQL) for prduction. > > Does XWiki have the other reasons recommending Tomcat? > > @WhyKesarr. MetaDeveloper. > "Keep the modifications due to a single change together in a predictable > range." > > 2012. 2. 14. 오전 2:31 "goldring, richard" > <richard.goldr...@uk.thalesgroup.com> 작성: > > > Hi Andrey, > > > > You're running using Jetty and HSQL? I had similar problems and > eventually > > moved to Apache Tomcat and MySQL which are more memory efficient - > suggest > > you to the same although I don't lnow if there is another way but I > exported > > my pages to .xar files which I had to break into small .xar file in > order to > > reimport into my new xwiki on Tomcat and MySql (I kept the two > installations > > running until we were happy we had copied everything across ... This > process > > wasn't easy! > > > > Hope that helps. > > > > Regards, > > > > Richard > > > > -----Original Message----- > > From: users-boun...@xwiki.org [mailto:users-boun...@xwiki.org] On > Behalf Of > > Crowd Covered > > Sent: 13 February 2012 17:21 > > To: users@xwiki.org > > Subject: [xwiki-users] Performance tuning for growing wiki > > > > Hi guys, > > > > Thanks again for great collaborative tool! > > > > We currently have about 1200 pages inside, many with objects, where > several > > people search/read/edit info every day. And we are experiencing > performance > > problems - at least once a day, sometimes more often wiki becomes > > unresponsive for 3-10 minutes while having high CPU load (my guess is > either > > page file swapping or garbage collection by JVM), Out Of Memory errors > > becoming more often (sometimes wiki is stable for 1-2 weeks, sometimes > fails > > several times a day). Additionally we've got repeating problems even with > > quite small attachments 500Kb-2Mb (I am aware of x27 DB storage trouble) > > > > According to recommendation in guides and some talks on the Internet I > tend > > to try database tuning or change. Could you please recommend a good > > candidate among freely available databases or even give a hints on HSQLDB > > tuning (maybe changing default memory mode to cached)? I've taken a look > at > > H2 vs. HSQLDB comparison but there are quite controversial opinions... > > > > Current servlet container configuration is -Xms700m -Xmx700m, no tuning > for > > database, computer is a virtual machine on a farm with 2 GHz CPU and 1 Gb > > RAM. BTW, is this in general expected behavior for such configuration? > > > > Many thanks, > > Andrey > > _______________________________________________ > > users mailing list > > users@xwiki.org > > http://lists.xwiki.org/mailman/listinfo/users > > _______________________________________________ > > users mailing list > > users@xwiki.org > > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users@xwiki.org > http://lists.xwiki.org/mailman/listinfo/users > -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
