awrigh11 commented on issue #3499: URL: https://github.com/apache/accumulo/issues/3499#issuecomment-1594627039
> I think that part is expected... and would have occurred with batching in 1.10 using a JVM with less memory. In 2.1, batch sizes are determined explicitly through configuration. We found this to be much more reliable (and a substantially simpler implementation) than the auto-batching based on available memory, which did not always work well if the JVM was resizing or during some Java GC cycles. The configurable batch sizes should allow more control over the size of the batches you want to process, and you can tune your JVM memory accordingly. This issue and the user's requirement to choose their own batch size was specifically called out [with its own paragraph in the 2.1.0 release notes](https://accumulo.apache.org/release/accumulo-2.1.0/#better-accumulo-gc-memory-usage). Yeah I would agree. I just wanted to be clear that our 3x slow down was not related to batching. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
