NodeResult websocket queries scale linearly due to history

Bug #1752754 reported by Lee Trager
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Lee Trager
Fix Committed

Bug Description

The NodeResult websocket returns ScriptResult information. Part of the metadata sent over the websocket is historic results. While the websocket can retrieve the latest ScriptResults in a constant number of queries getting the historic results requires one query per ScriptResult. Thus the current query count is 3 + n.

Historic results are not seen by default on any page in MAAS. These results could be retrieved using a separate websocket function. This will reduce the load on the region and database when viewing ScriptResults.

Tags: performance

Related branches

Changed in maas:
importance: Medium → High
tags: added: performance
Changed in maas:
milestone: 2.4.x → 2.4.0beta1
importance: High → Critical
Changed in maas:
assignee: nobody → Lee Trager (ltrager)
Lee Trager (ltrager)
Changed in maas:
status: Triaged → Won't Fix
status: Won't Fix → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.