16 Oct
2009
16 Oct
'09
11:05 a.m.
It seems to me, Xwiki 2.0 has a memory leak (see memory increase form
week 41 to week 42).
Virtual memory for jsvc process has increased to almost 1GB.
Valdis
16 Oct
16 Oct
11:16 a.m.
Hi Valdis,
On Oct 16, 2009, at 11:05 AM, Valdis Vītoliņš wrote:
It seems to me, Xwiki 2.0 has a memory leak (see
memory increase form
week 41 to week 42).
Did you attach something to your mail?
Virtual memory for jsvc process has increased to
almost 1GB.
We need someone to look into this by using a profiler. We have some
yourkit licenses for xwiki committers.
What would be great is if we could turn on profiling for the
myxwiki.org farm and allow remote profiling to it.
Jerome, is that something we could work on together on?
Thanks
-Vincent
11:37 a.m.
Valdis,
On Oct 16, 2009, at 11:05 AM, Valdis Vītoliņš wrote:
It seems to me, Xwiki 2.0 has a memory leak (see
memory increase form
week 41 to week 42).
Virtual memory for jsvc process has increased to almost 1GB.
One thing to note is that it's normal that the memory increases if the
document cache is not filled for example.
By default this cache stores 100 documents (unless you've modified the
xwiki.store.cache.capacity property in xwiki.cfg).
Thus the size of the memory will vary with the size of the documents
in this cache too. If you have a big doc of 10MB in the cache the
total memory used will be larger by 10MB.
BTW to flush the cache you can call $xwiki.flushCache() (you need
programming rights) and check the memory after the flush.
Thanks
-Vincent
5508
days inactive
5508
days old
2 comments
2 participants
participants (2)
-
Valdis Vītoliņš -
Vincent Massol