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

Performance for gutenberg blocks on post detail pages #277

Open
menno-ll opened this issue Jan 8, 2025 · 0 comments
Open

Performance for gutenberg blocks on post detail pages #277

menno-ll opened this issue Jan 8, 2025 · 0 comments

Comments

@menno-ll
Copy link
Member

menno-ll commented Jan 8, 2025

We have projects where it seems that the more blocks we add, the slower the project gets.
And when I did run qcachegrind on a project experiencing performance issues, 1 thing stood out.

What stands out is that there seems to be some space to gain if in Block_Manager.php determine_block_type_class we would do less calls to class_exists().
What i guess we can do is add a static property, or make the class a singleton.
Then, we can maybe use some local caching to not have to do this check for every block.
As well that we then will skip the other filters as well, adding extra potential slowdowns.

image

@menno-ll menno-ll changed the title Performance on post detail pages Performance on gutenberg blocks post detail pages Jan 8, 2025
@menno-ll menno-ll changed the title Performance on gutenberg blocks post detail pages Performance for gutenberg blocks on post detail pages Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant