[COMPASS-5648] Investigate ace editor component performance Created: 31/Mar/22 Updated: 27/Oct/23 Resolved: 31/May/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Performance |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergey Petushkov | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Documentation Changes: | Not Needed | ||||||||
| Sprint: | Iteration Anemone, Iteration Cuttlefish | ||||||||
| Description |
|
Switching to aggregation tab / or to the JSON view for documents creates a massive, very noticeable UI lag in Compass, this is caused by ace editor mounting multiple components on the page. This is something that was existing in Compass for awhile now, but as we now planning to allow for a quick back and forth switch between editing and running the pipeline, this becomes a much more noticeable issue. We should investigate if anything can be done about that and find an approach that will allow us to have a smoother UI in Compass when ace editors are on the screen |
| Comments |
| Comment by Rhys Howell [ 31/May/23 ] |
|
We're now on code mirror so this has gone away 🙌 |