Stupid, stupid question (memory saving)

[Ernio]

Yeah, I can count (and I did some math and testing via System.currentTimeMillis(), but still, I just NEED to ask before I get to work.

I need to either save global array[biome][depth][value] or I need to make this array every time it is needed.

Size is: array[20][256][100000] which will give us 51.200.000 values. Best compression available for my algorithm to work is byte (I prefere short). Now: Holding so many values in global array will take some MB of RAM (well not just some, a lot compared to rest of my mod). Is it better to just lose this memory and have full access to it all the time, or maybe to create whole array from for()for()for(), use it, and delete (memory saving and stuff).

 

Algorithm is called everytime you destroy block (holy fuck that often, and I think that answers the question, but just give me your opinion)

[Draco18s]

Da fuk you need that much data for?

[TheGreyGhost]

Hi

 

51 MB is not so much.

 

But maybe your algorithm can be more efficient and not need so many anyway.  What are you trying to do?

 

-TGG

 

 

[Ernio]

Well... just fuck it (sry), I've tried to make something too realistic, but such an accurate thing just can't exist in clean code, I'll just go with some freaky-close randoms system with some changing variables. That will be challenging maybe Excel will help

<CLOSED> (sorry, explaining this mechanism would be too hard, and I belive that me spending week on it is alredy too much - and yeah, it's complicated math-mod)

As I said I'll just creat close-value-function somehow ;O

[GotoLink]

Save the thing.

Redoing the calculation would be a waste of computing power, since you can't be sure the memory is freed every time you remove the reference in Java.