Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: add stress-test for blocks performance #10340

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

revnelson
Copy link

What?

Adds a Pages collection to the _community test. The Pages collection has 50 blocks with 25 container blocks that can each contain the 50 standard blocks.

Why?

Projects with many blocks (especially the nesting with container blocks) lead to agonizingly slow admin navigation. I started a discussion to see if these can get cached in a similar fashion to the lexical features that greatly improved frontend navigation when using richText fields.

I'm currently using 35 blocks with 9 container blocks in a real-world project. It's in production with Payload v2. The large number of blocks leads to 15-30min HMR and build times in v2. In v3, HMR and build is much faster, but admin navigation is unusable.

How?

By generating 50 blocks and 25 container blocks that are used in a new Pages collection. Navigation in the admin dashboard grinds to a near halt.

@AlessioGr AlessioGr self-assigned this Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants