B4J Question How to access byte array as int/short value directly without overhead?

You can use RandomAccessFile.Initialize3 to read numeric types from arrays of bytes.

Thanks Erel, I will look at it. Don't even know the RandomAccessFile can access byte arrays.

kimstudio said:

ByteConverter can do this

Click to expand...

You won't get faster than using ByteConverter to map byte arrays to and from other types. Most methods are a thin wrap of Java ByteBuffer that is optimised for such accesses.

Thanks agraham. I digged the ByteConverter thread and found the thin wrap in the source code as you indicated:

IntBuffer ib = ByteBuffer.wrap(bytes).order(endian).asIntBuffer();

Not sure Internally how it works but looks mostly like the C/C++ pointer concept, that's great.

Maybe I am too obsessed to one or two milliseconds faster which I should not concern for modern computers

kimstudio said:

Maybe I am too obsessed to one or two milliseconds faster which I should not concern for modern computers

Click to expand...

If you are doing CV, it is worth actively considering reducing the overhead

kimstudio said:

IntBuffer ib = ByteBuffer.wrap(bytes).order(endian).asIntBuffer();

Not sure Internally how it works but looks mostly like the C/C++ pointer concept, that's great.

Click to expand...

Use one of the function calls to "map" Bytes to Ints, and then see if changes to one are reflected by changes in the other, ie are they using the same memory locations?

If not, then the Java function is allocating and copying memory, and no degree of wrapper thinness is going to magic that away.

Although, speaking of magic, I do recall that MMUs can make one area of memory look like two (subject to page address alignment) and defer the allocation and copying until changes (writes) are made to one of the "duplicated" memory pages.

edit: I also vaguely recall being able to memory-map files as arrays under VAX VMS, and I believe what it did was map the file pages as paged-out memory pages, and then later the file would read from disk by the usual virtual memory handler when the array was accessed, no extra effort required.

emexes said:

If not, then the Java function is allocating and copying memory, and no degree of wrapper thinness is going to magic that away.

Click to expand...

Completely makes sense.

I did check Java doc and I think it's related to "Direct vs. non-direct buffers" and "original buffer and view buffer". It is a little bit complicated. I may play with ByteBuffer later.

kimstudio said:

I may play with ByteBuffer later.

Click to expand...

There is also potentially another roadbump on your quest for ultimate efficiency, being that I suspect multi-dimensional arrays are actually arrays of arrays of elements, rather than a single contiguous block of all the elements.

I should probably check this out before casting aspersions (lol no pun intended), but I figure: let's see how long it takes for me to be corrected (if I'm wrong). ?