Using directives in Cms Blocks / Cms Pages is causing same data loaded multiple times from Country and Region classes.

[jakwinkler]

Preconditions and environment

Magento 2.4.5
Magento 2.4.6-p1

Steps to reproduce

0. Disable Block HTML & Full Page HTML cache
1. Create a CMS Block / CMS Page,
2. Create multiple directives to display some links or data using the store URLs or some config data

{{store url=""}}
{{config path="web/secure/base_url"}}

3. For the fun of it, do it 200 times
4. Profile the page with black fire / other profiling tool

Expected result

Directory / Region is loaded only once during the page load

Actual result

Directory / Regions are loaded by the number of entries in the CMS Block / Page

{{store url=""}}
{{config path="web/secure/base_url"}}

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @qsolutions-pl. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @qsolutions-pl,

Thank you for the report and collaboration!

We have tried to reproduce this issue on 2.4-develop.
Please refer the screenshot below:

We have made 25 entries to the cms Page and the getCountryId method is being called 25 times, but as the Block HTML & Full Page HTML cache are disabled isn't this the expected behaviour?

Please let us know the use case for the same.

Thank you.

[jakwinkler]

In my personal opinion, this should be cached on the Collections or model level and the data should be cached.
This is generating too many database queries and
Maybe create an array to return already cached/fetched elements by ID?
I'm not sure what is the best solution here, but the fact the same query can be called multiple times for the same data, is an issue

[engcom-November]

Hello @qsolutions-pl,

Thank you for the quick response!

We also tried to reproduce this by enabling the cache, still we are getting too many database queries.
Hence confirming the issue.

Thanks.