Re: [xwiki-users] Performance tuning for growing wiki
On Thu, Feb 16, 2012 at 1:54 PM, Crowd Covered wrote: > I've solved the problem I asked about yesterday: Column length too big for > column 'XXX' (max = 21845); use BLOB or TEXT instead > There is a useful option in MySQL Migration Tool to change the SQL code for > table creation, so I've just used LONGTEXT instead of VARCHAR(6) and > alike which are not valid for MySQL. > Additionally I needed to fix several dates in XWIKIDATES like -04-16 > 00:00:00 into 2012... - no idea why they were treated as invalid... > > Could someone also hint about consequences of several errors I wasn't able > to solve? May be they can be solved as well? > > 1. For XWIKIATTACHMENT_ARCHIVE I got 0 of 20 entries transferred, with > an error "Unknown column '0x' in 'field list'". Indeed in .script file I > see them like this: INSERT INTO XWIKIATTACHMENT_ARCHIVE > VALUES(-2145604653,''). I believe it's safe to ignore this? But how did it > happen? > 2. Same error for XWIKIATTACHMENT_CONTENT, but there only one row should > have been deleted - may I got problems because of this? > > Will community benefit from description of such HSQLDB->MySQL migration or > was it a non-trivial thing for me only (I only faced databases during > university course)? :) If yes where can I add it? I would like to see a Migration section on http://platform.xwiki.org/xwiki/bin/view/AdminGuide/ . Thanks, Marius > > 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
Re: [xwiki-users] Performance tuning for growing wiki
I've solved the problem I asked about yesterday: Column length too big for column 'XXX' (max = 21845); use BLOB or TEXT instead There is a useful option in MySQL Migration Tool to change the SQL code for table creation, so I've just used LONGTEXT instead of VARCHAR(6) and alike which are not valid for MySQL. Additionally I needed to fix several dates in XWIKIDATES like -04-16 00:00:00 into 2012... - no idea why they were treated as invalid... Could someone also hint about consequences of several errors I wasn't able to solve? May be they can be solved as well? 1. For XWIKIATTACHMENT_ARCHIVE I got 0 of 20 entries transferred, with an error "Unknown column '0x' in 'field list'". Indeed in .script file I see them like this: INSERT INTO XWIKIATTACHMENT_ARCHIVE VALUES(-2145604653,''). I believe it's safe to ignore this? But how did it happen? 2. Same error for XWIKIATTACHMENT_CONTENT, but there only one row should have been deleted - may I got problems because of this? Will community benefit from description of such HSQLDB->MySQL migration or was it a non-trivial thing for me only (I only faced databases during university course)? :) If yes where can I add it? Andrey ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Performance tuning for growing wiki
Thanks for all who replied to my initial request. I've followed the advice and tried MySQL. I have heard about problems with xar export/import and would like to avoid it if naked DB migration is possible. I've googled up what seems a righteous way using MySQL Migration Toolkit (here are 2 links: http://confluence.atlassian.com/display/DOC/Migrating+from+HSQLDB+to+MySQL, http://wiki.alfresco.com/wiki/Migrating_from_HSQL). After some exercises to make jdbc driver work I've got database exported but run into problems with particular columns because of which complete tables are not copied to MySQL. Below is an excerpt from report where for problematic tables evil columns are mentioned: `PUBLIC`.`XWIKICLASSES` Column length too big for column 'XWO_CUSTOM_MAPPING' (max = 21845); use BLOB or TEXT instead `PUBLIC`.`XWIKICLASSESPROP` Column length too big for column 'XWP_CUSTOMDISPLAY' (max = 21845); use BLOB or TEXT instead `PUBLIC`.`XWIKICOMMENTS` Column length too big for column 'XWC_HIGHLIGHT' (max = 21845); use BLOB or TEXT instead `PUBLIC`.`XWIKIDOC` Column length too big for column 'XWD_CONTENT' (max = 21845); use BLOB or TEXT instead `PUBLIC`.`XWIKILARGESTRINGS` Column length too big for column 'XWL_VALUE' (max = 21845); use BLOB or TEXT instead `PUBLIC`.`XWIKIPREFERENCES` Column length too big for column 'XWP_MENU' (max = 21845); use BLOB or TEXT instead Is there a way to cope with this or the only way is export/import with Large Wiki Export extension? Thx, Andrey ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Performance tuning for growing wiki
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 변형진 > 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" > 작성: > > > 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
Re: [xwiki-users] Performance tuning for growing wiki
I forgot to say, on curriki.org, which is under very high demand, we use the Sun Java Application server on solaris engines. Using Glassfish is likely to give similar results. paul Le 13 févr. 2012 à 20:39, Paul Libbrecht a écrit : > As a personal experience, more based on habits, tomcat is of real good > quality most of the times. > Things like encoding must be cared for early... but that is easy to make. > > i2geo.net is used quite commonly and runs tomcat 7 (with my own scripts... > but I do not think that makes a big difference). > > paul > > Le 13 févr. 2012 à 19:05, Sergiu Dumitriu a écrit : > >> 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" >>> 작성: >>> >>>> 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 >> >> >> -- >> Sergiu Dumitriu >> http://purl.org/net/sergiu/ >> ___ >> 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
Re: [xwiki-users] Performance tuning for growing wiki
As a personal experience, more based on habits, tomcat is of real good quality most of the times. Things like encoding must be cared for early... but that is easy to make. i2geo.net is used quite commonly and runs tomcat 7 (with my own scripts... but I do not think that makes a big difference). paul Le 13 févr. 2012 à 19:05, Sergiu Dumitriu a écrit : > 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" >> 작성: >> >>> 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 > > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > ___ > 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
Re: [xwiki-users] Performance tuning for growing wiki
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" 작성: 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 -- Sergiu Dumitriu http://purl.org/net/sergiu/ ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Performance tuning for growing wiki
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" 작성: > 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
Re: [xwiki-users] Performance tuning for growing wiki
On Feb 13, 2012, at 6:30 PM, goldring, richard wrote: > 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! Using the large import/export tools on extensions.xwiki.org should make this much easier. I don't know if there are tools to move a DB from HSQLDB to MySQL. Thanks -Vincent > 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
Re: [xwiki-users] Performance tuning for growing wiki
Hi Andrey, On Feb 13, 2012, at 6:21 PM, Crowd Covered wrote: > 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… If you're currently using HSQLDB then it's "expected" that you'll have performance issues. It's not meant for production use. You should use MySQL, PostgreSQL, Oracle for example. We recommande MySQL since that's the database we test the most on. > > 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? Your max perm size isn't good. Recommendation is on: http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HPrerequisites Thanks -Vincent ___ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
Re: [xwiki-users] Performance tuning for growing wiki
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
[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
