Closed jrmaingo closed 2 years ago
This was bugging me as well; apparently golang just uses a lot of virtual memory (doesn't really affect actual real memory usage though)
from the faq:
The Go memory allocator reserves a large region of virtual memory as an arena for allocations. This virtual memory is local to the specific Go process; the reservation does not deprive other processes of memory.
If you look at the memory usage with something that shows RES memory usage (e.g. htop
if you have opkg
on your remarkable), it's more like 10KB :)
Refs:
Thanks for the reply! I'll close this issue for now then
Thanks for making this tool! It works well on my RM2 but I noticed that the memory usage seems excessive for a fairly simple program so I thought we could collect ideas on how to improve this.
I've attached a snapshot of
top
as an example I saw. My device finished syncing 10 articles and then I checked top so I wonder if the memory is not free'd up after the sync finishes. Thoughts?