Infra

Version 1.5 by Thomas Mortagne on 2020/05/20 15:42
Warning: For security reasons, the document is displayed in restricted mode as it is not the current version. There may be differences and errors due to this.

This page give details related to the setup sustaining myxwiki.org which is used by the XWiki Dev Team as a real life test of a very big XWiki instance.

Numbers

MyXWiki.org is a single XWiki instance currently containing Failed to execute the [velocity] macro. Cause: [The execution of the [velocity] script macro is not allowed in [xwiki:Infra.WebHome]. Check the rights of its last author or the parameters if it's rendered from another script.]. Click on this message for details.
wikis.

Container and hardware

  • maximum memory allocated to the JVM: 2048m (not huge but one of the points of MyXWiki.org is to make sure XWiki is not too bad at handling memory)
  • 5 cores 2.8GHz on a physical server
  • installed/upgraded using XWiki Debian packages
  • MariaDB 10.3
  • Tomcat 9

Performance related customizations

Remote Solr instance

The kind of volume myxwiki.org have to deal with does not fit well with the Solr embedded mode so we had to use a dedicated Solr standalone instance located on a different server.

  • maximum memory allocated to Solr JVM: 2048m
  • 2 cores allocated by VMWare

xwiki.cfg

  • xwiki.store.cache.capacity=800
  • xwiki.store.migration=0 (checking migration takes a very long time for )
  • xwiki.stats=0

xwiki.properties

  • notifications.rest.poolSize=4

hibernate.cfg.xml

  • <property name="hibernate.dbcp.maxTotal">200</property>
  • <property name="hibernate.dbcp.maxIdle">20</property>

Other interresting customizations

xwiki.cfg

  • xwiki.virtual.failOnWikiDoesNotExist=1
  • xwiki.virtual.usepath=0
  • xwiki.authentication.cookiedomains=myxwiki.org

xwiki.properties

  • wiki.alias.suffix=myxwiki.org
  • logging.deprecated.enabled=false