xwiki-devs December 2013

xwiki-devs@xwiki.org

33 participants
56 discussions

[xwiki-devs] French translation: congratulations!

by xrichard

Hi, I want to personnaly congratulate "raluca moisa" for the big work and the top quality of the french translation he is currently doing on http://l10n.xwiki.org. There are now less than 50 strings to translate in french. I'm confident we could together reach 100% in the coming week. Thanks again ;-). PS: I hope "raluca moisa" has subscried to this mailing list because I have no other way to contact and congratulate him for the hard work done -- View this message in context: http://xwiki.475771.n2.nabble.com/French-translation-congratulations-tp7588… Sent from the XWiki- Dev mailing list archive at Nabble.com.

11 years

[xwiki-devs] [Feedback] Extension Manager (+ Distribution Wizard)

by Ecaterina Moraru (Valica)

Hi, I'm gathering feedback about our Extension Manager [1] and implicitly about Distribution Wizard [2]. The purpose of this feedback request targets: - Acknowledgment that the features are working as expected and they solve the initial problems; - Raising new use cases and feature requests for them in order to improve productivity, usability, performance, etc.; - Any other problems/issues/feedback related to these topics. I will gather some conclusions on this page http://design.xwiki.org/xwiki/bin/view/Proposal/ExtensionManagerUseCases Thanks, Caty [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Extension+Manager+Appl… [2] http://platform.xwiki.org/xwiki/bin/view/Features/DistributionWizard

11 years

[xwiki-devs] How to load VelocityEngine in Java for a custom macro

by Matthias Wegner

Hello Devs, i try to use a custom template in a macro and didn't get the template loaded. I tried System.getProperty("user.dir") with "webapps/xwiki/templates/custom.vm". I always get the message "unable to find resouce in resource loader". Can you give me a hint how i load a correct VelocityEngine to load a template in the "templates"-directory. Regards, Matthias -- View this message in context: http://xwiki.475771.n2.nabble.com/How-to-load-VelocityEngine-in-Java-for-a-… Sent from the XWiki- Dev mailing list archive at Nabble.com.

11 years

[xwiki-devs] XWiki MSQL Support

by Richard Hierlmeier

most of our customers use MSSQL as database system. From time to time we have the opportunity to establish XWiki in customer projects. However it is difficulty and risky to recomment XWiki on a database system that is not supported by XWiki.org. What are the reasons for not supporting MSSQL? Is it simply a license or resource problem? Can we contribute here something? Richard

11 years

[xwiki-devs] Preliminary memory analysis of xwiki.org dump of 2013-12-01

by vincent＠massol.net

Hi devs, Yesterday xwiki.org crashed and I had configured it to take a heap dump. I’ve done a quick analysis that I’m sharing here (I’ll continue to analyse): Memory retained: 1GB Main contenders: 1) Document cache: 178MB 2) Lucene WeightedSpanTermExtractor: 166MB 3) IRCBot Threads: 165MB 4) Velocity RuntimeInstance: 38MB 5) SOLR LRUCache (Lucene Document): 38MB 6) EM DefaultCoreExtensionRepository: 38MB 7) NamespaceURLClassLoader: 23MB I’ve started analyzing some below. 1 - Document Cache Analysis ======================= * There are 3552 XWikiDocument in memory for 195MB * The document cache size is 2000 on xwiki.org * Large documents (such as Test Reports) take 6MB each (XDOM caching) * So if we had only large documents in the wiki the cache would need 2000*6MB = 12TO * I don’t think this cache is memory aware, meaning it doesn’t free its entries when memory is low * 178MB for 2000 docs means average of 89K per document. Huge variation between docs with big content and docs with no or small content This means that when memory is low on xwiki.org it should be enough to call a few pages with some large content to get an OOM. 4 ideas to explore: Idea 1: Use a cache that evicts entries when some max threshold is reached ** Infinispan doesn’t support this yet: https://issues.jboss.org/browse/ISPN-863 and https://community.jboss.org/thread/165951?start=0&tstart=0 ** Guava seems to support size-based eviction with the ability to pass a weight function: http://code.google.com/p/guava-libraries/wiki/CachesExplained#Size-based_Ev… Idea 2: Another idea is a usage of a distributed cache such as memcached or elasticsearch. I wonder if the overhead of the network communication is too high to make it interesting vs not caching the XDOM and rendering it every time it’s needed. Idea 3: Try to reduce even more how the XDOM is stored in memory Idea 4: Don’t cache the XDOM and render every time and use a title cache for titles. Also do that for getting sections. I think they are the 2 main uses cases for getting the XDOM. As a short term action, I’d recommend to immediately reduce the document cache size from 2000 to 1000 on wiki.org or double the heap memory. 2 - Lucene WeightedSpanTermExtractor Analysis ===================================== I’m not sure what this is about yet but it looks strange. * There is 166MB stored in the Map<String,AtomicReaderContext> of WeightedSpanTermExtractor. * That map contains 192 instances * Example of map items: “doccontent_pt” (2.4MB), “title_ru” (1.8MB), “title_ro” (1.8MB), etc Any idea Marius? 3 - IRCBot Analysis =============== * We use 3 IRCBot threads. They take 55MB each! * The 55MB is taken by the ExecutionContext * More precisely the 55MB are held in 77371 org.apache.velocity.runtime.parser.node.Node[] objects I need to understand more why it’s so large since it doesn’t look normal. I also wonder if it keeps increasing or not. 5 - SOLR LRUCache Analysis ======================= * It’s map of 512 entries (Lucene Document objects). 512 is the cache size. * Entries are instances of DocSlice Looks ok and normal. 6 - EM DefaultCoreExtensionRepository Analysis ====================================== * 38MB in "Map<String, DefaultCoreExtension> extensions” * 33MB in org.codehaus.plexus.util.xml.Xpp3Dom instances (44844 instances) which I guess corresponds to the pom.xml of all our core extensions mostly. Looks normal even though 33MB is quite a lot. 7 - NamespaceURLClassLoader Analysis ================================ * 23MB in org.eclipse.jgit.storage.file.WindowCache * So this seems related to the XWiki Git Module used by the GitHubStats application installed on dev.xwiki.org This looks ok and normal according to http://download.eclipse.org/jgit/docs/jgit-2.0.0.201206130900-r/apidocs/org… Thanks -Vincent

11 years

[xwiki-devs] About how to import the source code into eclipse.

by zhefangwu

I just want import the project to eclipse. But there are some errors during maven compile. Where can I find some help to do so? 发自我的 iPhone

11 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs December 2013