Closed akhenry closed 7 months ago
Solution notes as of January 2024: "Performance" Mode
Unlimited Mode
https://github.com/nasa/openmct/issues/7147 with row number always visible
Testathon 2/8/2024
Testathon 2024-02-08: verified NOT fixed, has multiple issues:
We should change the UI like this:
Edit properties
dialog.openmct.js:2 TypeError: Cannot read properties of undefined (reading 'toString') at Object.unsubscribe (openmct-yamcs.js:1:17241) at of.<anonymous> (openmct.js:2:3047277) at $m.destroy (openmct.js:2:3033914) at lI.removeTelemetryCollection (openmct.js:2:4209443) at lI.addTelemetryObject (openmct.js:2:4204604) at openmct.js:2:4207563 at Array.forEach (<anonymous>) at lI.clearAndResubscribe (openmct.js:2:4207545) at lI.updateTelemetryMode (openmct.js:2:4203500) at Proxy.handleConfigurationChanges (openmct.js:2:4177157)
More testing is above comment: https://github.com/nasa/openmct/issues/7268#issuecomment-1998560136
Make sure none of that is true anymore.
Verified fixed | Open MCT Version | Memory | CPU |
---|---|---|---|
3.2.0 | 222MB | 50.2 | |
4.0.0 | 117 | 4.2 |
Is your feature request related to a problem? Please describe. Telemetry Tables use far too much CPU and memory, even with a single telemetry point at 10Hz.
eg. Create a 10 Hz SWG and drop it into a telemetry table. Open Chrome task manager and observe that CPU usage is 100+% and memory usage is over 500MB.
Describe the solution you'd like I think that a 70% reduction in CPU utilization and at least 50% reduction in memory usage is achievable.
rowIndex
should be all that we need to trigger reactivity.