You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/02/11 01:17:56 UTC

[jira] Issue Comment Edited: (MRM-589) investigate performance issues with initial scan on a large repository

    [ http://jira.codehaus.org/browse/MRM-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209715#action_209715 ] 

Brett Porter edited comment on MRM-589 at 2/10/10 6:17 PM:
-----------------------------------------------------------

between the metadata changes not requiring scanning as much, and looking into improving the scanning code (perhaps based on Ant 1.8's improvements?) we can resolve this for 1.4

      was (Author: brettporter):
    between the metadata changes and looking into improving the scanning code (perhaps based on Ant 1.8's improvements?) we can resolve this for 1.4
  
> investigate performance issues with initial scan on a large repository
> ----------------------------------------------------------------------
>
>                 Key: MRM-589
>                 URL: http://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
>
>
> 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.
-
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