theigl opened a new issue, #1950: URL: https://github.com/apache/fury/issues/1950
### Question Since https://github.com/apache/fury/commit/01f1b66383a127a801f22ebe7fac5ca54d675878 Fury's internal `MemoryBuffer` is reset to 128k after every use. The change makes sense because it reclaims memory that could otherwise sit unused, *but* it will cause massive allocations if most of the object graphs you serialize are >= 128k. In this case, a new buffer is allocated for every serialization. In my application, most object graphs are 64k-512k leading to very frequent reallocation of the built-in buffer. Currently, my only option is to manage a pool of `MemoryBuffers` myself and pass them to Fury instead of relying on the built-in buffer, but this makes using Fury *significantly more complex*. Would it make sense to make the buffer size limit configurable? In my case, a 1MB limit would be ideal. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
