Major Description
Just came across this.
The size estimation is: (limit + offset) * estimatedEntrySize
with just the passed limit and offset, and this estimate is applied for each single scan.
This is way too pessimistic when a large limit is passed as just a safety measure.
Assuming you pass 10.000.000. That is the overall limit, but Phoenix will apply it to every scan (at least one per involved region) and take that much memory of the pool.
Not sure what a better estimate would be. Ideally we'd divide by the number of involved regions with some fuss, or use a size estimate of the region.
Attachments
Issue Links
- links to