[NIFI-9309] Improve UI responsiveness

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.15.0
• Component/s: Core Framework, Core UI
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 19/Oct/21 00:20
• Updated: 20/Jun/22 18:06
• Resolved: 23/Oct/21 23:42

Description

There are a few different small improvements that can be made to the backend that will result in far better UI performance in some situations:

• Include a uiOnly query parameter when the request is made to fetch the flow for a ProcessGroup. This can filter out specific fields such as processor properties & property descriptors. If the UI passes in this query parameter, we can avoid populating much of the DTO objects. This means the request is much smaller so in a cluster, it's much less to deserialize/parse/serialize when merging responses, and it means that the UI has a lot less json to parse.
• When attempting to access the Variable Registry for a given Process Group, we are very inefficient in how we determine which components are affected by a given variable. Instead of re-compiling the Expression Language for every property, we should do it only once and make that a part of the PropertyConfiguration object and make use of that.
• When obtaining the bulletins for a given component, we are also very inefficient. We iterate over many RingBuffer objects, filtering entities for each. But if we know the component & process group ID of the component whose bulletins we are interested in, we can instead just jump straight to the appropriate RingBuffer by fetching it from the Map.

Issue Links

• fixes: NIFI-9513 Trying To fetch variables in NIFI-UI , we see servlet , jersey spring and service unavailable with status 503 error
• fixes: NIFI-6900 Request to retrieve flow in clustered environment should be much less expensive
• is related to: NIFI-9368 Fix the ordering of the log entries on the processor level bulletin pop-up
• links to: GitHub Pull Request #5462