Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <16407003.1213190712972.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Wed, 11 Jun 2008 08:25:12 -0500 (CDT)
From: "Robin Roos (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Commented: (CONTINUUM-1528) Continuum gets slower over time
 and eventually crashes
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ http://jira.codehaus.org/browse/CONTINUUM-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138171#action_138171 ] 

Robin Roos commented on CONTINUUM-1528:
---------------------------------------

Hi Folks

I thought I suffered from this problem.  Then we added clean as one of the maven2 targets in our build definition.  (Without clean we were seeing deleted classes remain in our build product.)  Since adding clean I have seen stable performance from Continuum.

I hope that info helps some people.

Cheers, Robin.

> Continuum gets slower over time and eventually crashes
> ------------------------------------------------------
>
>                 Key: CONTINUUM-1528
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1528
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.1-beta-3
>            Reporter: Julien S
>            Priority: Critical
>             Fix For: 1.2
>
>         Attachments: ci.png, ci2.png, ci3.png
>
>
> Our instance of continuum gets slower over time.
> We counted the time needed to verify all projects at night when nothing has changed in the SCM (hence, nothing is built).
> During day time, the usage was quite intensive, however.
> On day 1, it was about 3 minutes
> On day 2, it was about 7 minutes
> On day 3, it was about 10 minutes
> And after a few more days (perhaps a week or so), Continuum would constantly generate OutOfMemoryError and stop working.

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