Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ace-dev@incubator.apache.org
Date: Wed, 16 Feb 2011 10:38:57 +0000 (UTC)
From: "Karl Pauls (JIRA)" <jira@apache.org>
To: ace-dev@incubator.apache.org
Message-ID: <9044732.20243.1297852737486.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (ACE-116) The server and the target logstores cause
 high cpu and memory load for big logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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