This mod reduces the memory usage of Minecraft in a few different ways. A high-level technical description of the changes is available here. I am working on getting at least some of these changes added to Forge, if and when a feature is merged into Forge I will remove it from the Forge version of this mod (the Fabric version will keep the feature).
The amount of memory saved will depend on the pack, in version 1.2.0 of the 1.16.4 Direwolf20 pack it reduces the memory usage (after GC) on the title screen roughly from 3.1 GB to 1.1-1.2 GB.
The project picture is a cropped version of this picture.
FAQ
Can you backport this to [MC version before 1.16]?
No, I won't backport it. I do not consider it worth the effort, and would like to encourage people to use more recent versions.
Should I install this on the server or just on the client?
Some optimizations are client-side only, but there are some rather high-impact optimizations that are relevant on the server too. So you should install it on both sides.
Would you consider separating the forge and fabric versions onto separate pages?
Thank you for reading this.
can you please make this mod for 1.12? As 1.16 mc is a terrible stuttery piece of s.
In reply to pigporker:
I'm not planning to backport to 1.12 (or any other MC version before 1.16). On 1.12 FoamFix applies some similar optimizations, you should use that instead.
Is this mod useful on client and on server?
In reply to TeaJ4y:
Yes. Some optimizations are client-only (the ones related to models), but there are others that are relevant on servers as well.
nice mod, thanks for making it king
Is your mod inspired by Hydrogen, or did you write it yourself from the ground up? And are the two compatible, or do they both target the same optimizations?
In reply to NebelNidas:
It's completely independent, except for part of the code used to load custom classes in google's package (the custom classes themselves are independent and very different from the ones Hydrogen has).
They are compatible in the sense that you can use both at once without breaking one of them (as far as I can tell), in version 2.0.2 of FC and above. The amount of memory saved by the combination is not optimal yet: they are compatible because I disable two features when Hydrogen is installed. For quad deduplication this is not a problem since H does more aggressive quad deduplication already. For the blockstate neighbor map it would be nice to be able to change that at some point, but I'll need to talk to the CaffeineMC people about that.
Thanks for the detailed answer! However, I've found a bug when combining FerriteCore with Hydrogen and Adorn, I've posted the issue on GitHub: https://github.com/malte0811/FerriteCore/issues/7
Hi malte! you are a freaking genius, this mod should be implemented in forge for its great usefulness, you take all the honors, keep it up!!!!
ferritecore is currently causing issues with snow rendering for me. i took out just about every performance mod i had in my modpack while trouble shooting this issue, and ferritecore - the last one i thought to try mind you - is most definitely the culprit.
take a snow tile, stack a single "block" / layer of it (this is hard to phrase properly, place the snow tile a single time, not the 8 times that would create a full block), and then stack another snow tile adjacent to it at either 2 or 4 height. you can now see through the side of the snow tile. this was causing massive performance dips in snowy biomes with terraforged due to how it generates.
not sure if this is a conflict with another mod, if you'd like my mod list i can post it in a little bit
In reply to dmsw0303:
I'm working on fixing this, in the future please report bugs on Github (the "Issues" link at the top).
using your mod in my modpack testing it reduces the ingame memory but increases the windows memory used
Buildtech LTE 3 - Modpacks - Minecraft - CurseForge
unknown.png (653×80) (discordapp.com)
unknown.png (410×86) (discordapp.com)
In reply to SDUBZ_:
What is the "windows memory usage" without FerriteCore? The value mostly depends on how much memory you allocate to MC (5 GB in this case), Java will generally grab all of that over some time and not give it back. The JVM has some overhead, and some things (mostly rendering-related, but also some networking things) are allocated outside of the 5 GB you allocated. That's why you're seeing more than 5 GB being used. FC does not affect any of the off-heap allocations (the ones that are not counted for the 5 GB), so I would be surprised if installing FC significantly increased the "windows memory usage".
Is this only client side or should it be run server side as well?
In reply to areallybigdeal:
Most optimizations only affect the client (since they deal with models), but there are a few high-impact optimizations that are also applied on the server. So you should run it on both sides.
can you make 1.15.2?
In reply to poguslav47:
No, I'm not planning to port to any previous versions of MC.
In reply to malte0811:
ok thanks
1.12.2 please !