[
https://issues.apache.org/jira/browse/NIFI-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-5241:
-----------------------------
Fix Version/s: 1.7.0
Status: Patch Available (was: Open)
> When calculating stats for components, use synchronized methods instead of
> atomic variables
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-5241
> URL: https://issues.apache.org/jira/browse/NIFI-5241
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.7.0
>
>
> Currently, the EventSumValue that is used to calculate stats for components,
> such as bytes in, bytes out, etc. using AtomicLong's and AtomicInteger's, etc
> to keep track of values. This made sense at first when there were only a few
> stats. Now, however, they hold about 17 different values and the atomic
> updates / atomic reads are more expensive than a synchronized method would
> be. This can cause sluggishness in the UI after the instance has been running
> for a while, especially if there are a lot of processors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
