Optimize for low memory use?

[GSI]

I'm using Miniflux v2.2.1 with ~30 feeds on an old Raspberry Pi. Typically I have some 150 MB of RAM available.

It used to run fine, but recently the OS has to kill the program regularly:

[1383230.652600] Out of memory: Killed process 16052 (miniflux.app) total-vm:554492kB, anon-rss:137368kB, file-rss:4kB, shmem-rss:0kB, UID:985 pgtables:168kB oom_score_adj:0

I suspect that these crashes may be related to having set some feeds to "fetch original content" - which I only recently learned about. I'm not sure though.

As a first mitigation attempt I set BATCH_SIZE=1, but that didn't prevent the OOM's.

[jvoisin]

Wow, this is odd. My instance is only using 40MB of ram, and I have a lot of feeds :/

[asilentdreamer]

For me miniflux in docker consistently uses 30-50 mb ram, while postgres can go over 150 when refreshing lots of feeds at once. I have little under 400 feeds.

[rdelaage]

Maybe it would be interesting to find where this huge memory consumption come from. A way to to that would be to use the go profiler (https://go.dev/blog/pprof)

[rdelaage]

@GSI Did you achieve to find what is consuming a lot of memory in your setup? If not, you can run pprof like that (it will require to build a custom version of Miniflux)

diff --git a/internal/http/server/httpd.go b/internal/http/server/httpd.go
index c7428a32..3ed8ee1e 100644
--- a/internal/http/server/httpd.go
+++ b/internal/http/server/httpd.go
@@ -9,6 +9,7 @@ import (
        "log/slog"
        "net"
        "net/http"
+       _ "net/http/pprof"
        "os"
        "strconv"
        "strings"
@@ -207,6 +208,8 @@ func setupHandler(store *storage.Storage, pool *worker.Pool) *mux.Router {
                w.Write([]byte(version.Version))
        }).Name("version")
 
+       router.PathPrefix("/debug/pprof/").Handler(http.DefaultServeMux)
+
        if config.Opts.HasMetricsCollector() {
                router.Handle("/metrics", promhttp.Handler()).Name("metrics")
                router.Use(func(next http.Handler) http.Handler {

And you can draw the memory usage graph like that go tool pprof -http :7879 http://localhost:7878/debug/pprof/heap (replace with the relevant addresses, and open the web ui in a web browser)

[GSI]

Thank you, that's an interesting tool. I just enabled it and will have to wait until the next OOM occurs.

The last one was 8 days ago, even though I have miniflux configured to update a single feed every 30 minutes (export BATCH_SIZE=1 and export POLLING_FREQUENCY=30).

[GSI]

In the meantime I had two OOM's, but I it seems pprof doesn't keep a history?

[rdelaage]

the profiler doesn't keep anything. You need to poll it using a command like that go tool pprof -http :7879 http://localhost:7878/debug/pprof/heap. Of course before the OOM, so for example if it get OOM killed each 1 week, you can poll after 6 days when it still running