I've been considering the optimization of two of my latest data storage techniques in Java, and would like to know which is really the most memory-efficient. Below are descriptions of the two classes. For the sake of argument, assume they have the same methods for interfacing with the data, which allow the user to get or set the state of any of the bits individually or by range via the following methods:
public boolean getBitState(byte bitIndex)
bitIndexpublic Clazz setBitState(byte bitIndex, boolean newState)
bitIndex to newState and returns the resulting objectpublic int getStateOfBits(byte startIndex, byte endIndex)
startIndex and endIndex as an intpublic Clazz setStateOfBits(byte startIndex, byte endIndex, int newState)
startIndex and endIndex to the value provided in newState.newState has fewer bits than fit, it is made to fit by adding zeros to the leftnewState has more bits than fit, the excess bits (on the left side) are croppedThese are the classes I have made to utilize this interface:
This class uses an int as a way of storing 32 bits of data through bitwise functions.
This class uses an array of 32 booleans as its way of storing 32 bits of data through standard array interactions.
Use an int and bitwise functions! Most JVMs will represent an array of boolean as an array of bytes. java.util.BitSet uses internally an array of longs to represent it's bits (chunks of 64).
Have you considered using the BitSet class? It seems like it does everything you need to do, and is probably well optimized, memory-wise.
Considering your two choices, definitely not an array of booleans. And array of boolean requires extra memory space for the metadata associated to the datatype. Plus, most JVM will allocate 32 bits of memory for each boolean.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With