[
http://jira.codehaus.org/browse/MRM-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200153#action_200153
]
Marc Lustig edited comment on MRM-1291 at 12/2/09 2:43 AM:
-----------------------------------------------------------
I forgot to mention that this "periodic peaks" load-pattern occurs only from
time to time.
I. e. when the pattern happens, the peaks occur periodically. But after
restarting Archiva, the pattern does not occur anymore for a couple of days or
weeks.
I can be sure about this because we have notifiers installed that warn when a
certain HTTP-request on Archiva exceeds a certain threshold value.
We have not seen alarms between 3rd of november and 30th of november.
On the 30th out of a sudden the periodic load raised tremendously.
I doubt the RDBMS being slower could have an impact on the load.
was (Author: axismundi):
This pretty much sounds like a reasonable explanation - unfortunately it
may not be the (only) reason.
I forgot to mention that this "periodic peaks" load-pattern occurs only from
time to time.
I. e. when the pattern happens, the peaks occur periodically. But after
restarting Archiva, the pattern does not occur anymore for a couple of days or
weeks.
I can be sure about this because we have notifiers installed that warn when a
certain HTTP-request on Archiva exceeds a certain threshold value.
We have not seen alarms between 3rd of november and 30th of november.
On the 30th out of a sudden the periodic load raised tremendously.
I doubt the RDBMS being slower could have an impact on the load.
> Archiva has periodic load-peaks
> --------------------------------
>
> Key: MRM-1291
> URL: http://jira.codehaus.org/browse/MRM-1291
> Project: Archiva
> Issue Type: Bug
> Components: system
> Affects Versions: 1.2.2
> Environment: RHEL4, Oracle RDBMS
> Reporter: Marc Lustig
> Attachments: cpu-day.png, screenshot-1.jpg
>
>
> Archiva causes periodically an increased system-load. (see Munin-stats
> attached)
> During these peaks calling the homepage takes around 6 secs, whereas normally
> it is around 1 sec.
> I could not identify corresponding messages in the logs.
> Could somebody else observe this?
--
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
