ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (ACE-116) The server and the target logstores cause high cpu and memory load for big logs
Date Wed, 16 Feb 2011 10:46:57 GMT

     [ https://issues.apache.org/jira/browse/ACE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Pauls resolved ACE-116.
----------------------------

    Resolution: Fixed

I commited a fix for this. The target seems very stable now (memory and cpu is low all the
time while the log is still growing and even a 5mb log doesn't change that).

The server is a stable with a low load in terms of cpu but still has some memory spikes (but
a lot better than before). 

I resolve this issue as it seems good enough for now.

> The server and the target logstores cause high cpu and memory load for big logs
> -------------------------------------------------------------------------------
>
>                 Key: ACE-116
>                 URL: https://issues.apache.org/jira/browse/ACE-116
>             Project: Ace
>          Issue Type: Improvement
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>
> When big logs (for example the auditlog after a lot of updates) are around, the server
as well as the target starts to show very high cpu and memory loads. The memory is not due
to a leak as such but there is just a lot of garbage created pretty much constantly. I'm seeing
up to all available memory and 100% cpu load on both server and target after a while if there
is a big log (this is independent of whether the log is still growing or not - it just needs
to be big). 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message