Transition from 'cache-size' to 'max-memory' in detaspace v2.4.0: impact on memory usage under high concurrency
Determine if the 'max-memory' configuration effectively caps heap usage under sustained high-concurrency load in detaspace v2.4.0+. Because the project’s roadmap notes an unresolved decision about enabling asynchronous garbage collection hints by default, it is unclear how this setting interacts with the new memory limit. Does enabling asynchronous garbage c
detaspace