Could there be "bridge" between records and this API - eg. to get memory layout for record which would allow to store records (or record data actually not the instance itself) in off-heap memory.
One thing I don't understand is why when I used direct buffers, I would still get out of memory errors trying to allocate relatively small amounts of memory, as if it was still trying to grab memory off the Java heap. This is on Android at least I see this behaviour. I had to make my own 'native buffer' class which allocates memory via malloc in C over JNI and returns a buffer object back to Java. I thought allocateDirect was supposed to do this for me but apparently on Android it does not.
It's limited to 64 MiB by default on desktop: stackoverflow.com/questions/3773775/default-for-xxmaxdirectmemorysize On Android default limit may be even smaller.
Could there be "bridge" between records and this API - eg. to get memory layout for record which would allow to store records (or record data actually not the instance itself) in off-heap memory.
Damn Brian is good. Takes over a presentation with 1 days notice and delivers it like he made the slides.
The slides were good until 32:35, typographic quotation marks.
One thing I don't understand is why when I used direct buffers, I would still get out of memory errors trying to allocate relatively small amounts of memory, as if it was still trying to grab memory off the Java heap. This is on Android at least I see this behaviour. I had to make my own 'native buffer' class which allocates memory via malloc in C over JNI and returns a buffer object back to Java. I thought allocateDirect was supposed to do this for me but apparently on Android it does not.
It's limited to 64 MiB by default on desktop: stackoverflow.com/questions/3773775/default-for-xxmaxdirectmemorysize On Android default limit may be even smaller.
Is this going to work with the Vector API (JEP 338)?
Amazing!
Is the C2 patch released ?