[
https://jira.codehaus.org/browse/MRM-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280426#comment-280426
]
Brett Porter commented on MRM-589:
----------------------------------
The indexer shouldn't matter too much as it runs in parallel (though the
constant processing does slow other operations).
There are a few things to check:
- pure scan time (just to run through them all, but not do anything)
- scan time with metadata population
- scan time with consumers (e.g. indexing)
Currently the metadata population is done as a consumer, and it seems to have
gotten quite a bit slower in recent versions. Need to test it again with latest
trunk and identify the slow parts, then create separate issues to resolve
those. Performance will also depend on MRM-1327 so that needs to be tied up
first.
Important that this performs well on the first use, since all users upgrading
will have to go through it with their existing repositories.
> investigate performance issues with initial scan on a large repository
> ----------------------------------------------------------------------
>
> Key: MRM-589
> URL: https://jira.codehaus.org/browse/MRM-589
> Project: Archiva
> Issue Type: Task
> Affects Versions: 1.0-beta-4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.4-M1
>
>
> I've recently found scanning a copy of central to take several hours instead
> of <0.5hr that I'd expect.
> Should be easy to pinpoint hotspots and make this more efficient - it may
> just be a memory consumption issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
