Is there any production cache for mapper configs / attribute autoconfiguration?

[anasmorahhib]

Hi 👋

Thanks for the great library — I’m using SymfonyCasts/micro-mapper in a Symfony 7.3 project and it’s working really well.

I had a performance-related question regarding production use:

When using micro-mapper in prod environment, does the system cache any of the internal mapper configs or attribute parsing results? Specifically:

• On each request, is registerAttributeForAutoconfiguration() called and re-parsed?
• Or is there any internal caching mechanism for compiled mapper closures or metadata?
• If not, do you plan to support some kind of warmable cache layer in the future?

I’m wondering if the attribute scanning and mapper metadata generation has any performance impact on high-traffic APIs — or if it’s handled efficiently already (e.g. via Symfony’s container, or internal static cache).

Thanks in advance! 🙏

[bocharsky-bw]

Hey @anasmorahhib ,

Tough question, I'm not sure about the cache layers upstream in Symfony, but there's no cache code in this component itself. Probably, if performance is a crucial thing for you, I would recommend that you do some load testing. You probably could place some logging code in the spots like registerAttributeForAutoconfiguration() to see if that's called and re-parsed every time, because I don't have an answer off the top of my head.

No specific plans for introducing some cache layers in the future, but if that's something some people needed - we don't mind adding it. PRs are warmly welcome to improve the component.