+1, I've got problems with caching in netbeans integration. Managed to lower the long term memory usage significantly by resetting the ProjectBuildingRequest on the MavenProject instance. That one was holding quite a few Model instances, I''ve looked at the other caches but I was not entirely clear what the purpose is and scope.
For me there's 2 usecases fro the caching. 1. How to get rid of it when not required anymore 2. how to share safely across multiple invokations on different projects. Milos On Thu, Sep 6, 2012 at 12:51 PM, Kristian Rosenvold <kristian.rosenv...@gmail.com> wrote: > We have quite a few caches all over the place in our code base (and > some in plexus), quite a lot of them caching stuff based on this or > that class (or method). > > Almost all of them leak class references, as far as I can understand > bloating permgen requirements (and hence memory usage) of maven. > > Most of these cache would seem to be relevant at the "MavenExecution" > level, i.e. we could choose to ditch all of this at the end of each > build without loosing any real performance. Quite a few of these > caches use various "weak" type references but as far as I can see all > of them are flawed and still leak ;) > > It would seem to me like we could use some kind of injectable cache > scope that could be used, preferably bound to each execution. Anyone > have any ideas on how we could do this ? > > Kristian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
