I believe there are several issues
I don't know what caused memory usage increase in 3.1.1. Memory increase
in 3.2.3 is likely related to MNG-5669 [1]. Then there is general
inefficiency in how Maven represents project Model in memory.
The memory increase in 3.2.3 may be possible to workaround,
is there an issue to watch?
Thanks
Milos
On Fri, Oct 17, 2014 at 10:59 PM, Igor Fedorenko
wrote:
> I think I know the problem.
>
> Current master creates multiple MavenProject instances for the same
> parent pom, while 3.0.5 reused the same instance. I have not looked how
> hard this will be t
On 18 Oct 2014, at 10:10, Jörg Schaible wrote:
> thanks again for taking the time. Something must have gone wrong for an
> increased memory usage by 400% for the same stuff.
Interesting - this might explain why a lot of my builds are now blowing up our
build server ever since we started using ou
Hi Igor,
Igor Fedorenko wrote:
> I think I know the problem.
>
> Current master creates multiple MavenProject instances for the same
> parent pom, while 3.0.5 reused the same instance. I have not looked how
> hard this will be to fix yet.
>
> In, more generally, MavenProject implementation is f
I think I know the problem.
Current master creates multiple MavenProject instances for the same
parent pom, while 3.0.5 reused the same instance. I have not looked how
hard this will be to fix yet.
In, more generally, MavenProject implementation is far from efficient.
For example, each instance
Hi Igor,
Igor Fedorenko wrote:
> You can zip and email it to me directly or share it on github, dropbox
> or google drive and send me the link. I am flexible :-)
I've sent the small one directly ...
Cheers,
Jörg
-
To unsubscr
You can zip and email it to me directly or share it on github, dropbox
or google drive and send me the link. I am flexible :-)
--
Regards,
Igor
On 2014-10-16, 11:41, Jörg Schaible wrote:
Hi Igor,
Igor Fedorenko wrote:
Can you provide an example project we can use to reproduce the problem
loc
Hi Igor,
Igor Fedorenko wrote:
> Can you provide an example project we can use to reproduce the problem
> locally? You may be able to strip your source tree from everything bun
> pom.xml files, for example.
OK, this works out. I have now such a transportable setup. It's zipped about
1.1MB with
You could take some heap dumps and share them with me on google disk.
A baseline from the best one and one from the worst one. It would be
nice if you could get them at approx the same time in the build
Kristian
2014-10-16 15:20 GMT+02:00 Jörg Schaible :
> Hi Igor,
>
> Igor Fedorenko wrote:
>
>>
Hi Igor,
Igor Fedorenko wrote:
> Can you provide an example project we can use to reproduce the problem
> locally? You may be able to strip your source tree from everything bun
> pom.xml files, for example.
Interesting idea. I'll try if this works out.
- Jörg
-
Hi Jason,
Jason van Zyl wrote:
> Igor and I have been moving a vast project with hundreds of modules (200
> to 400 to 500) from 3.1.0 through 3.2.4-SNAPSHOT and don't observe this
> drastic change. We would definitely notice.
>
> Are all your plugin versions locked down in that they don't vary
Can you provide an example project we can use to reproduce the problem
locally? You may be able to strip your source tree from everything bun
pom.xml files, for example.
--
Regards,
Igor
On 2014-10-16, 5:12, Jörg Schaible wrote:
Hi folks,
we have a single build with currently ~400 projects (in
Igor and I have been moving a vast project with hundreds of modules (200 to 400
to 500) from 3.1.0 through 3.2.4-SNAPSHOT and don't observe this drastic
change. We would definitely notice.
Are all your plugin versions locked down in that they don't vary even though
the version of Maven does? A
Hi folks,
we have a single build with currently ~400 projects (incl. builders i.e.
POMs having modules only). We are already used to increase the provided
memory in MAVEN_OPTS, but lately we have troubles to build at all because of
OOMEs (heap). Look at following numbers building with the diffe
14 matches
Mail list logo
