Current architecture and idle resource behavior for single-user self-hosting

[aqsede]

Hello!

I’m planning to self-host Sure for personal finance tracking (single user setup).
From what I understand, the project originated from a system designed for a larger B2C customer base — likely involving background jobs, Sidekiq workers, and Redis for scalability and reliability.
Since the project was originally designed to support a large B2C customer base, I’d like to understand its current runtime footprint.

Specifically after everything is configured:

• How active are the background jobs or workers when the app is idle?

• What’s the typical CPU, memory, or database activity in such a setup?,

I’m mainly trying to get a clear picture of how “busy” the app remains in the background when not being actively used.

[jjmata]

If my development dev container is any indication, very little CPU action ... but Docker Desktop is probably not the best way to measure this.

This is on M1 Pro 16GB with 10 CPU cores available (so 1000% is "normal" per Docker metrics):