[
http://jira.codehaus.org/browse/CONTINUUM-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110453
]
Julien S commented on CONTINUUM-1528:
-------------------------------------
The two servers are alongside. The full check takes about 3 to 4 minutes when
nothing is built. I agree that's a fairly heavy load. But the two servers seem
to be able to cope with it. We do not do fresh builds of course !
Usually during day time, in a 15m interval there are just a few commits.
Continuum rebuilds them (and projects which depends on them) immediatly.
You seem to suggest that the queue would fill up till exhaustion ? It is true
that sometimes, the "next" schedule is triggered before the first one is
completed, but at night (when there is no commit), Continuum seem to be able to
process all the queue as it stops building and checking out projects (well,
before the next schedule, I mean).
> 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
>
> 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
