[Bug]: Memory usage after GC

[chmonyasik]

Before reporting

• I searched the existing issues and this has not already been reported.
• I am running the latest version of Neo Vitae available for my Minecraft version.

Minecraft version

1.21.1

NeoForge version

21.1.235

Neo Vitae version

neovitae-1.21.1-1.0.26

Description

Decided to test memory usage. In a flat world on NeoForge with no mods installed, about 600 MB remains in use after a GC cycle. Adding NeoVitae increases that by roughly 400 MB, so after each GC cycle the game consistently uses around ~1000 MB of memory.

Steps to reproduce

1. Install NeoVitae and its dependencies.
2. Join a world and observe how much memory remains after a GC cycle in the top-right corner.

Logs and crash report

Modpack or other mods

No response

[chmonyasik]

Actually, I'd also add that NeoVitae generates a huge atlas because of arrays. It might be worth reducing the resolution of those arrays. I also noticed that some of the array textures are already 16x16, but even those often contain multiple slightly different shades of white or unnecessary semi-transparent pixels

[Saereth]

the arrays have always been a problem in BM, as well as the atlas size in general and its definitely on my radar, we are in the process of redoing them all which will shrink the array size considerably, as well as several other of the assets.

I'll look into any other mem optomizations I can do and do some profiling this weekend

[Saereth]

did some work on this last night, reduced the atlas size by 54% already for next update, havent had a chance to get to the profiling yet but I should be able to this weekend