[IMPLEMENTED] Squidex - UI Form Delay

I have…

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [ ] Bug report
  • [x] Performance issue
  • [ ] Documentation issue or request

Current behavior

We parse PDF documents and the parsed contents gets stored in Squidex. The PDF is broken into passages and we’ve below schema to store it.

In this schema, “Name” and “Detail” field gets populated with the PDF content and editors will review these fields and type in values in “Comments” and “Keywords” fields. Both the “Comments” and “Keywords” are configured with “Input” editor.

Of late, when we type value in these fields, there is considerable delay for it to appear in the UI form. User has to wait for at least 30 secs or so to see the content they typed to appear in the UI form.

This seems to be an issue when the underlying PDF document size is in MBs. The larger the file, more the number of elements in the Sections array.

Expected behavior

User typed content should appear in the UI as and when they type it. There shouldn’t be any delay.

Minimal reproduction of the problem

Not sure of the exact step. But something like below should help in replicating.
Create a schema as mentioned with array as field type and populate it with 1000 items.


  • [x] Self hosted with docker (Kubernetes)
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: []


  • [x] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge



can you provide me a backup or something like that that helps me to reproduce it?

I’ve exported the back up but unable to attach it here since .zip extension is not allowed. Any other way to share the backup ?

Upload it to drive or so and send me the link as PM

I’ve sent a message with link.

Thank you, I will have a look. There is a chance, that it is not fixable, because the angular forms system is really slow.

Right now, I don’t see what I can do. The problem is mainly the layout phase in chrome:

It is interesting that not so many nodes actually need a new layout:


But the DOM is just too big.

I would write a custom editor and a grid framework that supports virtual scrolling.

A custom editor for the entire content ? Or, for fields within “Section” array ?
I’m not sure I understand what needs to be done here. Can you elaborate , please ?

Only for the section array:


I am also going to test a virtual scroll component for the array editor.

I have found a solution with virtual scroll.

Great !! Can you please share ?

Sure, there is a PR in the CI pipeline. When it is done I can give you the docker tag.

The build is still running, but once complete the tag is dev-6146

When you have more than 50 items in a array-item drag and drop will be disabled and virtual scrolling enabled.

Thank you, Sebastian. I will give it a try and let you know.

1 Like

Hi Sebastian,
I pulled down the latest tag, dev-6134, but still the issue exists. I’m still seeing the same delay while typing. This time around, Squidex is hosted on my local machine using docker-compose for testing. Below is the content of docker-compose.yml file. Can you take a look ?

version: '2.3'
    image: mongo:4.4.1
      - /etc/squidex/mongo/db:/data/db
      - internal
    restart: unless-stopped

    image: "squidex/squidex:dev-6134"
      - URLS__BASEURL=https://${SQUIDEX_DOMAIN}/
      - EVENTSTORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
      - STORE__MONGODB__CONFIGURATION=mongodb://squidex_mongo
      - ASPNETCORE_URLS=http://+:5000
      test: ["CMD", "curl", "-f", "http://localhost:5000/healthz"]
      start_period: 60s
      - squidex_mongo
      - /etc/squidex/assets:/app/Assets
      - internal
    restart: unless-stopped

    image: squidex/caddy-proxy
      - "8081:80"
      - "443:443"
      - SITE_SERVER="squidex_squidex:5000"
      - /etc/squidex/caddy/data:/data
      - /etc/squidex/caddy/config:/config
      - squidex_squidex
      - internal
    restart: unless-stopped
    driver: bridge

My bad. I see that you’ve mentioned dev-6146 as the tag. Let me try that and get back to you.

1 Like

@Sebastian - I pulled down the tag dev-6146 and I no longer see any delay in the UI form while typing. Everything works as expected. When will this change be part of the master branch ?

Thanks a lot for quick turn around, as always.

1 Like

It is part of the master branch.

This topic was automatically closed after 2 days. New replies are no longer allowed.