maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joakim Erdfelt (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MRM-465) [Load Testing] When asking for pages that require the effective-pom in high load, app becomes unresponsive.
Date Mon, 13 Aug 2007 19:37:47 GMT

     [ http://jira.codehaus.org/browse/MRM-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joakim Erdfelt updated MRM-465:
-------------------------------

    Attachment: archiva-OutOfMemoryError_during_jpox.log

I added an in-memory ehcache around the effective project creation phases, and got further
in my siege tests.

However now I experience an out of memory condition.
See attachment archiva-OutOfMemoryError_during_jpox.log for log.

> [Load Testing] When asking for pages that require the effective-pom in high load, app
becomes unresponsive.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: MRM-465
>                 URL: http://jira.codehaus.org/browse/MRM-465
>             Project: Archiva
>          Issue Type: Bug
>          Components: browser
>    Affects Versions: 1.0-beta-2
>            Reporter: Joakim Erdfelt
>            Assignee: Joakim Erdfelt
>            Priority: Critical
>         Attachments: archiva-OutOfMemoryError_during_jpox.log
>
>
> When having a process/tool (such as siege) hit the artifact browsing pages on archiva
in rapid succession, the archiva application becomes unresponsive.
> Possible reason: when the first request hits to get the effective pom, the build of that
effective pom starts, but before it has a chance to finish, another request arrives to do
the same thing, and the process starts again, resources and such get eaten up fast in that
scenario.
> Possible solution:
> * Lock the effective pom resolution on a per groupId:artifactId:version level.
> * Cache the effective pom on disk.
> ** (option 1) save the effective pom to disk in the groupId:artifactId:version location
using the extension ".effective.pom"
> ** (option 2) save the effective pom to a long lived ehcache (backed on disk, in ehcache
format)

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

        

Mime
View raw message