# Reducing Ignition Edge memory footprint **URL:** \ **Category:** Ignition\ **Created:** [September 20, 2022, 12:32am UTC](https://forum.inductiveautomation.com/t/reducing-ignition-edge-memory-footprint/64258 "2022-09-20T00:32:19Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![fshriver](https://avatars.discourse-cdn.com/v4/letter/f/db5fbb/32.png) [@fshriver](https://forum.inductiveautomation.com/u/fshriver)\ **Post date:** [September 20, 2022, 12:32am UTC](https://forum.inductiveautomation.com/t/reducing-ignition-edge-memory-footprint/64258/1 "2022-09-20T00:32:19Z")
We’re using Ignition Edge for some field work on devices with a very small compute budget (1GB of RAM or less). Ignition Edge appears to fit on these devices and performs decently, however it takes almost half the available RAM (~400-500 MB). Are there any strategies we can use to reduce the memory footprint at all? We’re already uninstalling all non-essential modules and setting `wrapper.java.maxmemory` to 256 under `data/conf`. Just wanted to ask if there’s any more aggressive measures we could be taking. ---
**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\ **Post date:** [September 27, 2022, 3:21pm UTC](https://forum.inductiveautomation.com/t/reducing-ignition-edge-memory-footprint/64258/2 "2022-09-27T15:21:48Z")
Hello fshriver, You may be able to configure more aggressive garbage collection, but with that little memory, the GC should already be pretty aggressive. You’ll also need to be mindful of what your system is doing. You’ll need to minimize device connections and the number of tags on the system. Allocating that little memory may cause issues and 1GB of RAM is the minimum to meet Edge system requirements. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/4/a4f7914064d4e026828f149a9e21cb1461e8a97d.png)