4 ms·
Now everyone will tell you that you can use ByteBuffer or sun.misc.Unsafe to keep memory off-heap and hence out of sight of the GC. BUT what that means is that
by fauigerzigerk 13y ago
Now everyone will tell you that you can use ByteBuffer or sun.misc.Unsafe to keep memory off-heap and hence out of sight of the GC.
BUT what that means is that you have create your own custom implementations of the data structures you need and you'll have to write your own memory allocator.
Unless that memory area holds just a simple data BLOB (like a video file) you're always going to be much more productive implementing the entire thing in C++.
- pjmlp 13y ago> Unless that memory area holds just a simple data BLOB (like a video file) you're always going to be much more productive implementing the entire thing in C++. Or use a GC enabled systems programming language, that provides control over what is allocated via GC or via other means.