-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Description
Search before asking
- I searched in the issues and found nothing similar.
Description
Java dynamically adjusts the batch size target per table based on observed actual batch sizes - grows 10% when batches fill past 80%, shrinks 5% when below 50%, clamped to [2 * pageSize, maxBatchSize]. This right-sizes memory reservations for tables with small rows. We currently use a fixed writer_batch_size for all tables. The impact is less critical for us than Java since our memory limiter is semaphore-based (no physical page pool), but it would still improve memory budget utilization.
Willingness to contribute
- I'm willing to submit a PR!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels