maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] (MERCURY-119) Mercury optimization
Date Tue, 25 Nov 2014 21:39:25 GMT


Michael Osipov closed MERCURY-119.

    Resolution: Won't Fix

Please refer to
if you're wondering why this issue was closed out.

Assignee, if you think you can fix this bug anytime soon, please reopen and proceed appropriately.

>  Mercury optimization
> ---------------------
>                 Key: MERCURY-119
>                 URL:
>             Project: Mercury (retired)
>          Issue Type: Improvement
>          Components: Misc/All
>    Affects Versions: 1.0-alpha-8
>            Reporter: Oleg Gusakov
>            Assignee: Oleg Gusakov
> This is a todo list to keep track/share optimization ideas 
> * VirtualRepositoryReader - refactor readArtifact() into 3 pieces, eliminate readArtifactsNoBatch().
> ** read qualified artifacts (we know the repository they are in)
> ** read virtual artifacts - SNAPSHOT/LATEST/RELEASE
> ** read the rest: not qualified real versions
> * implement negative cache [MERCURY-116]. Work started, need to add creation of negative
record in case of bad metadata bypass
> * ? cache version lists for resolved artifacts. This will help to prevent re-parsing
of POMs in MavenDependencyProcessor
> * ? make storing of pom bytes in the artifact optional / compress them
> * add evict() call to the metadata cache
> * implement LRU strategy in the metadata in-memory cache
> * pool HttpClient instances in the VirtualRepositoryReader and RemoteRepoWriterM2 instead
of closing them
> * review remote repository strategy regarding reading available versions. It now tries
to replace virtuals with actual version thus trying  to read metadata for all virtuals. Time
consuming on clean local repository and with lack of negative metadata caching

This message was sent by Atlassian JIRA

View raw message