[
https://issues.apache.org/jira/browse/NIFI-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501823#comment-16501823
]
ASF GitHub Bot commented on NIFI-5241:
--------------------------------------
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2752#discussion_r193081251
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-jetty/src/main/java/org/apache/nifi/web/server/JettyServer.java
---
@@ -689,6 +689,7 @@ private void configureGenericConnector(Server server,
HttpConfiguration configur
serverConnector.setHost(hostname);
}
serverConnector.setPort(port);
+ serverConnector.setIdleTimeout(60000);
--- End diff --
Assuming these changes are related to the frequency of the automatic
browser refresh, should we make this timeout relative to the value configured
in `nifi.ui.autorefresh.interval`.
> 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)
