Feature Request: RAM Usage Optimization for 16 GB Systems #738

Closed
opened 2026-11-08 19:15:31 +00:00 by doomAWL2 · 3 comments
doomAWL2 commented 2026-11-08 19:15:31 +00:00 (Migrated from github.com)

The idea

High RAM allocation overhead leads to severe performance degradation on system configurations with 16 GB of RAM.

While running build v2.0.2 (latest), system RAM utilization maxes out at 100%. Meanwhile, GPU and CPU usage remain far below capacity in the 50% to 80% range.

In the starter area (Kokiri Forest), this memory bottleneck results in extreme frame drops:

Standing still: 10–15 FPS

Moving around: 3–7 FPS

Optimizing memory footprint, implementing asset garbage collection, or introducing configurable texture/asset streaming buffers would significantly improve playable performance for users on 16 GB systems.

Anything else

System Specs:

GPU: NVIDIA GeForce RTX 4060

CPU: Intel Core i7-4790

RAM: 16 GB DDR3 @ 1600 MHz

Hookshot Build: v2.0.2

Note: The high RAM utilization issue is not isolated to DDR3 memory. Users running 16 GB DDR4 configurations experience identical 100% memory saturation, maintaining higher framerates solely due to higher RAM bandwidth. Lowering the base memory overhead or providing aggressive cache purging options would fix this bottleneck across 16 GB setups.

### The idea High RAM allocation overhead leads to severe performance degradation on system configurations with 16 GB of RAM. While running build **v2.0.2** (latest), system RAM utilization maxes out at 100%. Meanwhile, GPU and CPU usage remain far below capacity in the 50% to 80% range. In the starter area (Kokiri Forest), this memory bottleneck results in extreme frame drops: **Standing still:** 10–15 FPS **Moving around:** 3–7 FPS Optimizing memory footprint, implementing asset garbage collection, or introducing configurable texture/asset streaming buffers would significantly improve playable performance for users on 16 GB systems. ### Anything else **System Specs:** **GPU:** NVIDIA GeForce RTX 4060 **CPU:** Intel Core i7-4790 **RAM:** 16 GB DDR3 @ 1600 MHz **Hookshot Build:** v2.0.2 Note: The high RAM utilization issue is not isolated to DDR3 memory. Users running 16 GB DDR4 configurations experience identical 100% memory saturation, maintaining higher framerates solely due to higher RAM bandwidth. Lowering the base memory overhead or providing aggressive cache purging options would fix this bottleneck across 16 GB setups.
poopoosauce commented 2026-11-08 19:18:51 +00:00 (Migrated from github.com)

This. It uses so much while trying to compile upon loading a save, or entering a new area, shoots my apu temp up to 95°! Not cool. Looks better but still does way too much.

This. It uses so much while trying to compile upon loading a save, or entering a new area, shoots my apu temp up to 95°! Not cool. Looks better but still does way too much.
Desconvidado commented 2026-11-08 19:43:35 +00:00 (Migrated from github.com)
Image

The process ram usage never goes above 8gb (linux), i think the ram issue is something related to windows.

<img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/45a79042-73cc-4257-b075-9aeaa3fb036e" /> The process ram usage never goes above 8gb (linux), i think the ram issue is something related to windows.
NotRexed commented 2026-11-09 05:55:03 +00:00 (Migrated from github.com)

Tracked in #995, follow there. That issue collects every report of low FPS while the GPU is not fully used, and shader stutter, and this one is linked from it with its GPU, version and log details. If it still happens on v2.0.6 (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher), please add a comment there with your hookshot_log.txt.

Tracked in #995, follow there. That issue collects every report of low FPS while the GPU is not fully used, and shader stutter, and this one is linked from it with its GPU, version and log details. If it still happens on v2.0.6 (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher), please add a comment there with your `hookshot_log.txt`.
Commenting is not possible because the repository is archived.
No milestone
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#738
No description provided.