feat: Optimize metadata-storage build with HashMap caching for O(1) lookups

[benminer]

Performance Optimization: Map-based Caches for Metadata Class Building

Problem

Our schema generation process was becoming exponentially slower as our schema grew, taking over a minute to complete in some cases. With our large schema containing ClassMetadata arrays ranging from 3,000 to 15,000 objects, the repeated .find() and .filter() operations within forEach loops were creating significant performance bottlenecks.

Solution

Implemented map-based "caches" during the metadata class build process to replace inefficient array operations. These caches are added as new variables on the MetadataStorage class, while preserving list-based attributes where required by existing components.

Impact

This optimization has dramatically improved performance as demonstrated by the following benchmarks:
before (using O(n) lookups)

buildClassMetadata: 31.353s
buildFieldResolverMetadata: 313.714ms
buildResolversMetadata: 1.429s

after (using O(1) lookups)

buildClassMetadata: 268.772ms
buildFieldResolverMetadata: 38.593ms
buildResolversMetadata: 126.305ms

Implementation Notes

• Maintained backward compatibility with components expecting list attributes
• Primary focus was eliminating costly .find() and .filter() operations within loop contexts
• Maps provide O(1) lookup time compared to O(n) for array operations

[benminer]

@MichalLytek Thanks for taking a look at this, tests should be fixed. The root issue was a lack of resetting the new cache state in the global metadata-storage instance, and I also ran into some weirdness of needing to reset the state in beforeEach blocks rather than beforeAll - state was bleeding into other tests leading to failures, but would pass when run in isolation.

[benminer]

@MichalLytek Bumping this, would love to get it merged 😄

[MichalLytek]

I promise I will try to find some time to review it 😉

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.59%. Comparing base (be33fd4) to head (800ffa3).
Report is 77 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1779      +/-   ##
==========================================
+ Coverage   95.50%   95.59%   +0.08%     
==========================================
  Files         113      114       +1     
  Lines        1847     1929      +82     
  Branches      364      366       +2     
==========================================
+ Hits         1764     1844      +80     
- Misses         83       85       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[benminer]

Hey @MichalLytek, bumping this again! Let me know if you get a chance to take a look. Thanks in advance.