Performance - Optimize getSpecificOptions triggered by all getAttributeText calls

[anthony-blackbird]

Description (*)

When performing a call to $product->getAttributeText('my_attribute') to output the text value of the attribute, it always trigger a call to database. I introduce a memoization to save the previously calculated result and avoid to call database each time for the same combination $storeId / $attributeId / $optionId

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Performance - Loading attribute options from DB  #36174

Manual testing scenarios (*)

1. Go to a page where getAttributeText is used depending of your templates files (category page, product page), for example, use getAttributeText('color')
2. If you have two or more products having the exact same color, only one call will be made to database
3. You can notice it by using Blackfire or a log in the newly introduced method loadSpecificOptions

Questions or comments

Contribution checklist (*)

• [*] Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @anthony-blackbird. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[anthony-blackbird]

While the PR is processed, I suggest this package I developed, compatible with Magento 2.4.x.

It also introduces a cache layer for these specific options loaded. I might add it to my PR if Magento Team is interested too. More details on the readme : https://github.com/blackbird-agency/magento-eav-optimize

[anthony-blackbird]

@magento run all tests