Hi @themadcodger@kbin.earth, thanks for opening the discussion on github.com/dedicatedcode/reitti/discussions/176.

As I mentioned there: It depends on your usage. Reitti on its own could probably run with 512MB of RAM. This would probably also work while ingesting data from one of the integrations. I doubt that imports of data, spanning more than one day, will work. We already stream the uploaded data but in the end, it has to go temporally into RAM. Either in Reitti itself or in Redis or in the DB.

For anyone interested. These are the numbers on my host for the stack idling and waiting for data.

ONTAINER ID   NAME                CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS
222a0ed74fe7   reitti-reitti-1     0.10%     392MiB / 30.77GiB     1.24%     221MB / 103MB     2.11MB / 35.4MB   87
76c9317352bc   reitti-postgis-1    0.00%     83.38MiB / 30.77GiB   0.26%     67.7MB / 144MB    66.4MB / 145MB    16
06747b08882d   reitti-rabbitmq-1   0.46%     154.8MiB / 30.77GiB   0.49%     84.7MB / 91.3MB   46MB / 86.4MB     57
5012afdf4688   reitti-photon-1     0.42%     492.6MiB / 30.77GiB   1.56%     124kB / 5.51kB    616MB / 256MB     121
ddbc854a3940   reitti-redis-1      0.50%     4.875MiB / 30.77GiB   0.02%     52.2MB / 232MB    2.34MB / 164kB    6