You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2016/02/19 20:49:18 UTC

[jira] [Updated] (NIFI-1541) Reduce memory footprint of components' stats

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

Mark Payne updated NIFI-1541:
-----------------------------
    Attachment: heap dump.png

> Reduce memory footprint of components' stats
> --------------------------------------------
>
>                 Key: NIFI-1541
>                 URL: https://issues.apache.org/jira/browse/NIFI-1541
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>         Attachments: heap dump.png
>
>
> Currently, when using the VolatileComponentStatusRepository,we see quite a lot of heap used up on the NCM for storing metrics. A heap dump shows that the majority of heap utilization is coming from the ComponentStatusReport class, each taking roughly 623 KB of heap space (roughly 450 processors, 450 connections). We store one of these 623 KB objects for each time that a "metrics snapshot" is captured - and we do this for each node in the cluster. This equates to gigabytes of heap space being used pretty quickly when running several nodes each with a couple hundred processors.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)