[jira] Commented: (MNG-2481) project builder should make the processed project cache configurable
[ http://jira.codehaus.org/browse/MNG-2481?page=comments#action_71584 ] Brett Porter commented on MNG-2481: --- WHM would be a good start, probably sufficient for some needs, but I also think having a caching plexus component of which one impl is a WHM would be nice too ;) I can see a possibility for wanting greater control over this to pre-emptively clean up memory. > project builder should make the processed project cache configurable > > > Key: MNG-2481 > URL: http://jira.codehaus.org/browse/MNG-2481 > Project: Maven 2 > Issue Type: Bug > Components: POM, Performance >Affects Versions: 2.0.4 >Reporter: Brett Porter > Fix For: 2.0.5 > > > the cache in the project builder is a simple map. This is usually fine for > Maven, but in long lived processes (Continuum, MRM, and I imagine the IDE > plugins as it gets used more) it can chew up quite some memory. > I'd suggest we make it configurable: > - can turn it on or off using plexus configuration > - can limit its size using plexus configuration > - can change other options, such as adding expiry ages to items regardless of > size > Rather than implementing something in the project builder itself, I suggest > having a cache plexus component that does everything we need it to (this > could be reused in the webapps as well). I'm not sure of any existing caching > solutions (I know OSCache has a general Java cache but don't know how > suitable it is). One alterantive might be to round out commons-cache with > some features and plexus descriptors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2481) project builder should make the processed project cache configurable
[ http://jira.codehaus.org/browse/MNG-2481?page=comments#action_71543 ] John Casey commented on MNG-2481: - Do you think this requires a full-blown caching solution, or will a WeakHashMap suffice? > project builder should make the processed project cache configurable > > > Key: MNG-2481 > URL: http://jira.codehaus.org/browse/MNG-2481 > Project: Maven 2 > Issue Type: Bug > Components: POM, Performance >Affects Versions: 2.0.4 >Reporter: Brett Porter > Fix For: 2.0.5 > > > the cache in the project builder is a simple map. This is usually fine for > Maven, but in long lived processes (Continuum, MRM, and I imagine the IDE > plugins as it gets used more) it can chew up quite some memory. > I'd suggest we make it configurable: > - can turn it on or off using plexus configuration > - can limit its size using plexus configuration > - can change other options, such as adding expiry ages to items regardless of > size > Rather than implementing something in the project builder itself, I suggest > having a cache plexus component that does everything we need it to (this > could be reused in the webapps as well). I'm not sure of any existing caching > solutions (I know OSCache has a general Java cache but don't know how > suitable it is). One alterantive might be to round out commons-cache with > some features and plexus descriptors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2481) project builder should make the processed project cache configurable
[ http://jira.codehaus.org/browse/MNG-2481?page=comments#action_71461 ] Brett Porter commented on MNG-2481: --- another thought - perhaps the cachability of poms that were accessed as parents or have been identified as dependencies could get a higher weighting since they are more likely to be reused later. > project builder should make the processed project cache configurable > > > Key: MNG-2481 > URL: http://jira.codehaus.org/browse/MNG-2481 > Project: Maven 2 > Issue Type: Bug > Components: POM, Performance >Affects Versions: 2.0.4 >Reporter: Brett Porter > > the cache in the project builder is a simple map. This is usually fine for > Maven, but in long lived processes (Continuum, MRM, and I imagine the IDE > plugins as it gets used more) it can chew up quite some memory. > I'd suggest we make it configurable: > - can turn it on or off using plexus configuration > - can limit its size using plexus configuration > - can change other options, such as adding expiry ages to items regardless of > size > Rather than implementing something in the project builder itself, I suggest > having a cache plexus component that does everything we need it to (this > could be reused in the webapps as well). I'm not sure of any existing caching > solutions (I know OSCache has a general Java cache but don't know how > suitable it is). One alterantive might be to round out commons-cache with > some features and plexus descriptors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
