Dynamic FPS vs FerriteCore
Dynamic FPS
modrinth.comFerriteCore
github.comSide by side
| Figure | Dynamic FPS | FerriteCore |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Self-hosted | — | Yes |
| Plans published | 0 | 1 |
| Spec score · Minecraft Performance Mods | 5.8 (#14) | 8.3 (#3) |
Plans
In their own words
Dynamic FPS
Dynamic FPS is a free Minecraft client mod focused on frame-rate performance. It supports multiple mod loaders and is listed for Minecraft versions from 1.14.3–1.14.4 through 26.3.0, including 1.15.x, 1.16.2–1.16.5, 1.17.x, 1.18.x, 1.19.x, 1.20.x, 1.21.x, 26.1.x, and 26.2.0. Sodium is not required. The project is available through its Modrinth page, and its pricing model is free with a free plan. The available description identifies its frame-rate focus but does not specify particular controls or a stated performance result. Version matching is therefore the main setup detail to check before installation. Users should select a listed game version and compatible mod loader for their client.
FerriteCore
FerriteCore is a free, MIT-licensed coremod for Minecraft: Java Edition that targets RAM use. It reduces memory associated with block states, models, predicates, strings, voxel shapes and baked quads through a set of documented optimizations. Examples include replacing block-state neighbor tables with FastMaps, caching multipart model predicates, deduplicating model instances and reducing baked-quad memory. The project reports that individual techniques saved hundreds of megabytes in cited tests; one pack example showed post-garbage-collection memory moving from roughly 3.1 GB to 1.1–1.2 GB on the title screen. Several optimizations have no CPU impact during play, while some add load-time CPU cost. ThreadingDetector optimization is disabled by default because it may very rarely cause race conditions. FerriteCore supports Fabric, Forge, NeoForge and Quilt and is listed for Minecraft Java Edition versions 1.16.5 through 26.3, depending on loader builds. It is marked for both client and server use, and the maintainer recommends installing it on both because some optimizations apply server-side. Versions before 1.16 are not supported for backporting.