Editing notebooks is extremely slow in the browser

Hi x_mark_x ,

Thank you for reaching out to the Fabric Community.

Based on your description, the lag may be influenced by factors such as notebook size, the number of imports, and resource utilization. Fabric Notebooks have certain limitations that might be relevant to your scenario:

• A maximum of 256 code cells can be executed in a single notebook.

• Notebook content size is limited to 32 MB.
• The upper limit for notebook activities or concurrent notebooks in notebookutils.notebook.runMultiple() is 50.

• The longest possible running job time is 7 days.

Please refer this link for more details: Fabric Notebook known limitation - Microsoft Fabric | Microsoft Learn

Since you are working with long notebooks and importing multiple functions, as you mentioned, dividing your notebook into smaller sections based on each wrangler/transformation object and limiting imports to only the necessary functions are great steps toward optimizing performance

Here is a similar thread: Solved: Notebook – input/keypress lagging when writing in ... - Microsoft Fabric Community

Please share any insights after testing these changes, and let us know if you need further assistance.

If this helps, kindly consider accepting it as the solution to assist other community members, and a kudos would be appreciated.

Thank you!

Best regards,
Vinay.
Microsoft Fabric Community Support.

---

x_mark_x wrote:

Hello there Fabricators!

 

I have an annoying issue when working with Notebooks in Fabric, namely that when I click on the code in a cell, there is a huge lag between the click and when the cursor appears in the code, or when i start to type, the letters appear much later than my input.
This lag can sometime even be 10 seconds!

 

This is not only annoying but can make editing of the code almost impossible at times.

This issue is present since i started to use Fabric.
I tried to minimize the number of open tabs in my broswer, but it does not seem to effect the performance.
Opening or interacting with other websites is as fast as expected, it is only the Fabric Notebooks that has this input lag.

Did anybody else face this issue, and if yes did you find any solutions to how this input lag can be minimized?

 

Thank you for your insights in advance!

---

Have you tried clearing your browser’s cache? That can help with performance sometimes, especially with apps like Fabric that store data. Another thing you could try is switching browsers. Sometimes Chrome or Firefox can handle things a little differently, and that could make a difference. Also, check if any browser extensions are slowing things down, Some of them, especially ones for security or ad-blocking, can have a big impact on performance.

If you haven’t already, make sure both your browser and Fabric are up to date, as they often release updates that improve things like performance. Lastly, maybe try working in an incognito window or close out some background processes to reduce the load on your browser.

Hi v-veshwara-msft,

I didn't forget this thread, but i had little time to test all the suggested solutions, plus i worked a little less in notebooks the last month.

When i noticed a slow response time in the notebooks in the browser, i firstly tried to get rid of all the cells where i had unnecessary code. I often experiment with different transformations in a separate notebook to be able to try out and test the validity of the transformations, and this notebook is always the longest. 

When i got rid of the unneccesary code, i (subjectively) experienced a faster response time within the notebook.

Also after restarting the computer or the browser i often experienced a little faster response time, which degraded over time, so my gut feeling tells me that concreterLiam's suggestion about clearing the cache in the browser might have positive effects, i still need to test this more thoroughly.

As said before, i will get back with more information when i had the time to test the other suggestions, but so far smaller notebooks seems to do the trick.