[PERF] Optimize REPORT requests by using batch MongoDB queries #141
+101
−41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Summary
getPropertiesForMultiplePathscalls with batch fetching usinggetMultipleCalendarObjects$ininstead of N sequential queriesChanges
getMultipleDAVItems()inlib/JSON/Plugin.phpto usegetMultipleCalendarObjects()when availablegetPropertiesForMultiplePathsfor nodes without batch support (e.g., SharedCalendar)docker-compose.test.yamlfor MongoDB and RabbitMQ to prevent test failuresPerformance Impact
Before: N sequential MongoDB queries (one per calendar object)
After: 1 batch MongoDB query with
$inoperatorFor an agenda with 100 events in a time range, this reduces from 100 queries to 1 query.
Test plan
Fixes #129
🤖 Generated with Claude Code