You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/11/11 15:58:35 UTC

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

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
             Fix For: 1.0


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

        

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-589:
-----------------------------

    Fix Version/s:     (was: 1.0)
                   1.1

> 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.1
>
>
> 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

        

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-589:
-----------------------------

         Assignee: Brett Porter
    Fix Version/s: 1.0

I will take one pass at this for 1.0 if there is anything obvious, then move off to 1.1.

> 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.0
>
>
> 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