20 Mar
2013
20 Mar
'13
5:17 p.m.
You didn't tell us if this wiki will be in production (ie, available to
many users, requiring to be up most of the time, with proper backup of
data, etc...) or if it's only a test wiki for you, for example.
If it's only for tests, the standalone wiki with jetty + hsqldb is good
enough, for production jetty is not recommended by xwiki I believe.
I can only give you a personal feedback : I have a wiki (in production)
with Tomcat 6 + MySql 5.1, with db attachments. The wiki has around 15000
pages now, and 1,6Go of attachments content in db (including all versions
of course). I plan to move to filesystem attachments, because during the
course and upgrades (this wiki started several years ago with version 0.9),
some attachments got corrupted for any reason, and it might be easier to
avoid/detect/repair with filesystem based attachments than db.
Apart from that, it works pretty well.
I don't think servlet container will have a big impact on the way big
attachments are managed, apart from possible limitations specific to each
container if they exist. The link I provided gives you what is supported by
xwiki, and with what it has been tested, but we can't decide for you what
container or rdbms to choose in the end :-)
BR,
Jeremie
2013/3/20 Hirji Patel <hirji.patel(a)akt-uk.com>
Thanks,
Which Servlet Container should I be using?
My DB will have large attachments and images.
Regards,
H
-----Original Message-----
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] On Behalf
Of Eugen Colesnicov
Sent: 20 March 2013 13:46
To: users(a)xwiki.org
Subject: Re: [xwiki-users] GlassFish + MySQL + Xwiki
Recommendations about DB & Container depend on Your scenario of XWiki
using ... For example, if you will have many and large attachments -
need to switch XWiki to "file-system attachments storage" or to use
another database (not MySQL) - this is my opinion.
My experience with big attachments - from the begging I have Windows +
Glassfish + Oracle (attachments stored in DB), after I migrated for
Linux + MySQL + Tomcat, but with file-system attachments storage - and
right now I prefer this variant - more speed and "lightness" ...
But, in any case, Your selection is not bad variant for production using
(for example comparative to other java servlets). Also you should
understand, that XWiki - it is not a BIG-BIG system, for example, likes
MS SharePoint. Same results & more speed you can get with more simple
hardware & software...
--
Best regards
Eugen Colesnicov
--
View this message in context:
http://xwiki.475771.n2.nabble.com/GlassFish-MySQL-Xwiki-tp7584387p758438
8.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. For more information on a proactive anti-virus
service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users