Errors in the workflow are making IDE sluggish

[sylwiabr]

Discord username

No response

What type of issue is this?

Permanent – Occurring repeatably

Is this issue blocking you from using Enso?

• Yes, I can't use Enso because of this issue.

Is this a regression?

• Yes, previous version of Enso did not have this issue.

What issue are you facing?

When I am working with bigger project and break it at the beginning first IDE is freezing for the time when errors are getting populated. Having many errors is also slowing down IDE when trying to work with it on weaker hardware (editing nodes, zooming, panning are having delays). Breaking first node on Restaurants example available in our templates is already freezing my IDE on M2 MacOS.

Expected behaviour

Errors on nodes should not affect IDE performance.

How we can reproduce it?

No response

Screenshots or screencasts

No response

Enso Version

nightly 12.05.2023

Browser or standalone distribution

Standalone distribution

Browser Version or standalone distribution

standalone

Operating System

Windows

Operating System Version

No response

Hardware you are using

No response

[hubertp]

That seems very much like a duplicate of #6639

[Akirathan]

This is a twofold issue:

• The first one is that IDE does have an unnecessarily long rendering of erroneous state.
• The second one is that the protocol between the IDE and Language server is not really ideal for these kinds of things - for rebuilding of a huge count of nodes.

[enso-bot]

Keziah Wesley reports a new STANDUP for the last Friday (2023-06-02):

Progress: Found an easy way to get a significant improvement. It should be finished by 2023-06-08.

Next Day: Next day I will be working on the #6674 task. Looking further into root causes (view invalidation)

[enso-bot]

Keziah Wesley reports a new STANDUP for today (2023-06-05):

Progress: While profiling, found that when a few visualizations are open they can quickly become the biggest time cost. Found this is partly due to inefficient handling of updates. It should be finished by 2023-06-08.

Next Day: Next day I will be working on the #6674 task. Implementing more efficient visualization updates.

[enso-bot]

Keziah Wesley reports a new STANDUP for today (2023-06-06):

Progress: Improved responsiveness with visualizations open by eliminating message deserialization as a performance bottleneck. It should be finished by 2023-06-08.

Next Day: Next day I will be working on the #6674 task. Additional performance improvements for visualizations changes.

[enso-bot]

Keziah Wesley reports a new STANDUP for yesterday (2023-06-07):

Progress: Working on some GUI bugs. Some work on fixing visualization-related slowness. It should be finished by 2023-06-08.

Next Day: Next day I will be working on the #6674 task. Finish current batch of bugs and performance improvements.

[enso-bot]

Keziah Wesley reports a new STANDUP for the provided date (2023-06-01):

Progress: Finished the #6544 PR; started profiling #6674. It should be finished by 2023-06-08.

[enso-bot]

Keziah Wesley reports a new STANDUP for the provided date (2023-06-08):

Progress: Fixed issue with eager visualization attachment, and finished PR. It should be finished by 2023-06-08.