Scope & Purpose

This PR adds memory monitoring mechanism to COLLECT method; hence AGGREGATE too. This PR assumes that supervised AqlValue will be implemented in the future. Currently, AqlValue created by CollectExecutors is NOT monitored.

• COLLECT method calls SortedCollectExecutor, HashedCollectExecutor, CountCollectExecutor or DistinctCollectExecutor. ResourceMonitor& is injected into each Executor (except CountCollectExecutor) at CollectNode.cpp.
• Once supervised AqlValue is implemented, usageScope will be no longer needed.

• AGGREGATE class now holds ResourceMonitor& and ResourceUsageScope (object by value). The usageScope is instantiated upon instantiating Aggregator; hence each Aggregator holds their own local usageScope.
• Even after supervised AqlValue is implemented, we still need local usageScope for Aggregator to monitor VPackSlice variables.

• 💩 Bugfix
• 🍕 New feature
• 🔥 Performance improvement
• 🔨 Refactoring/simplification

Checklist

• Tests
  • Regression tests
  • C++ Unit tests
  • integration tests
  • resilience tests
• 📖 CHANGELOG entry made
• 📚 documentation written (release notes, API changes, ...)
• Backports
  • Backport for 3.12.0: (Please link PR)
  • Backport for 3.11: (Please link PR)
  • Backport for 3.10: (Please link PR)

Related Information

(Please reference tickets / specification / other PRs etc)

• Docs PR:
• Enterprise PR:
• GitHub issue / Jira ticket:
• Design document: