bethibande / memoryapi

Hi there 👋

📫 How to reach me:

📧 [email protected]
 Bethibande#8532

memoryapi's Issues

File mapping

Add support for mapping files to memory.

Rewrite

This api needs to be entirely rewritten and restructured.
There have been too many workarounds/reimplementations of default behaviour of the IOAccess class.
The IOAccess is anything but ideal, it's causing performance issues by completing unecessary checks and more.
The rewrite should also include a builder class to replace all the static methods in the IOAccess class to allow for further customization.
Also, the def and impl modules should be merged, there is no longer a reason for these to be two seperate modules.

Access memory address

Add support for creating an access for reading/writing at a given memory address

Better native Memory performance

The IOScopedMemory class currently writes all data using MemorySegment.ofArray and then segment.copyOf(segment).
This is very slow and inefficient, especially when writing primitive values like integers.
MemorySegment.copyOf should only be used to write byte arrays or other types of arrays.
The IOScopedMemory class should use the MemoryAccess class to write these values instead.
There currently is no way for the IOAccessible class to handle these things, as the IOAccess class turns all primitive types into byte-arrays and then delegates the write to the IOAccessible.write(byte[], long, int) or IOAccessible.set(byte[], long, long, int) methods.

Performance

During a benchmark compare the performance of a Java ByteBuffer to an IOAccess. The IOAccess performance was considerably worse than the ByteBuffers performance, using heap byte arrays.
Also the MemorySegment performance doesn't seem very good either, perhaps replace this with a custom implementation using sun.misc.Unsafe

ByteOrder support

Add support for specifying a byte-order for reading/writing primitives.