I have performance issues with migrating from liip/theme-bundle to SyliusThemeBundle.
| vendor |
version |
| PHP |
7.4.12 |
| Symfony/Symfony |
4.4.15 |
| Sylius/SyliusThemeBundle |
2.2.0 |
| sonata-project/SonataAdminBundle |
3.76 |
Our project has more than 3 themes and we are using SonataAdminBundle. It has many twig template calls to rendering small blocks.
As a result, Sylius\Bundle\ThemeBundle\Twig\ThemeFilesystemLoader::locateTemplate is called more than 200 times per request.
Inside this method HierarchicalTemplateLocator rotating through all themes and all themed locators for each twig render call. It tooks very long time for such frequent calls.
In total, requests fall in timeout.
I have profiler screenshots to show my case (dev environment):

2 themes is configured

7 themes configured
one more screen - for CRUD list action, 2 themes configured:

Based on the above, for now I can't using this bundle for my project. I don't understand why this bundle is recommended to replacing for liip/theme-bundle.
I have performance issues with migrating from liip/theme-bundle to SyliusThemeBundle.
Our project has more than 3 themes and we are using SonataAdminBundle. It has many twig template calls to rendering small blocks.
As a result,
Sylius\Bundle\ThemeBundle\Twig\ThemeFilesystemLoader::locateTemplateis called more than 200 times per request.Inside this method
HierarchicalTemplateLocatorrotating through all themes and all themed locators for each twig render call. It tooks very long time for such frequent calls.In total, requests fall in timeout.
I have profiler screenshots to show my case (dev environment):
2 themes is configured
7 themes configured
one more screen - for CRUD list action, 2 themes configured:

Based on the above, for now I can't using this bundle for my project. I don't understand why this bundle is recommended to replacing for liip/theme-bundle.