Editor Slowness on Long Structured Text Content

Hi all,

We’re seeing very slow editing in the content admin— on one large article with ~5k words and many hyperlinks. The UI is blocked for long stretches while typing or interacting with the record.

What we’ve tried

  • Disabled plugins we suspected on a fork to see if the issue was our own plugins or third-party

  • Slowness seems to come from the editor via debouncing or some other main-thread blocking code via JS assets from assets.admin.datocms.com

We’re looking for guidance or recommendations here on mitigating editor performance for very long structured-text content.

Thanks!

@jason2,

Sorry about that. Could you please link me to the specific record & field name so I can take a look at it? (Every structured text field’s contents are a bit different, and we need to see what is actually in yours to be able to figure out what is causing the slowness.)

If you don’t want to post it publicly, you can DM me the URL or email support@datocms.com.

@jason2 Thank you very much!

That record is indeed extremely slow. I copied & pasted your text, minus the blocks, into a demo project for replication. And even there, with only that one field, the structured text was unusably slow.

I’ll let the developers know about this and update you once we have a better idea of what’s going on.

Sorry about that!

We’re making a bit of progress on this — we found a few optimization opportunities, but we need to more thoroughly test them to make sure we don’t introduce other regressions.

We’ll keep you updated.

Hey @jason2,

Could you please give this a try again? Thanks to your test case (a medium length document with a LOT of hyperlinks — believe it or not, that was just not a condition we’d encountered before!), we found and fixed a TON of related Structured Text performance issues. This was probably the single biggest change we made to the Structured Text editor in many years.

In our testing, it’s gone from unusably slow to lightning fast. Hopefully it’s the same for you now, but please let me know if any part of it is still slow, or if you notice any new bugs from the optimizations (hopefully not!).