On 02/13/2012 12:59 PM, 변형진 wrote:
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?
Personally I'm very happy with Jetty as well, and on the contrary, I'm
unhappy with some of the decisions taken by the Tomcat developers, which
IMO looks like a legacy project still sticking to last century's
standards, for "backwards compatibility". Sure, things can be
configured, like switching to UTF-8 for parsing the query string, or
disabling the %2F security warning, but still we get a lot of bug
reports caused by these default settings and people not reading the
installation guide for Tomcat.
@WhyKesarr. MetaDeveloper.
"Keep the modifications due to a single change together in a predictable range."
2012. 2. 14. 오전 2:31 "goldring, richard"
<[email protected]> 작성:
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: [email protected] [mailto:[email protected]] On Behalf Of
Crowd Covered
Sent: 13 February 2012 17:21
To: [email protected]
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
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
users mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/users
