On 2012-12-12 11:35 AM, Kristian Rosenvold wrote:
Does that mean m2e ditches the container every now and then?
No. m2e keeps the same container but injects its own cache
implementations that allows purging project-specific cache entries
whenever workspace project is re-read or removed from workspace. There
is also logic to dispose project realms.
m2e never releases plugin realms, but as I mentioned, this does not
cause any immediate problems so I have not spent much time on a solution.
In that case the whole unloading jason implemented can be reverted...?
That was actually my change Jason committed for me. I could not remember
my svn password at the time :-) The change was meant to deal with
classloader leaks during maven core IT execution in embedded mode. I was
getting OOME permgen pretty much immediately without this change. The
change did not cause any meaningful performance problems for me either
(I am still curious to know where the time difference comes from).
--
Regards,
Igor
K
Den 12. des. 2012 kl. 16:44 skrev Igor Fedorenko<[email protected]>:
>For tests, I think the easiest is to check number of realms at the end
>of each test and drop plexus container if it grew over certain number of
>realms. Pick the number large enough to fit in 128M of permgen and I
>think this will provide good tradeoff between performance and memory
>usage. This does mean separate container per each test thread, but I
>think this is required for other reasons.
>
>For IDEs, I would not try to guess what they need and let IDE developers
>come with proposed improvements to caching. I can't speak for other
>IDEs, but m2e for example, already deals with project realms properly
>and plugin realms are not usually an issue, so we don't really have any
>issues we need to fix.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
