Hello @764287,
Sorry for the delay in responding to you; lots of ‘stuff’ going on here (both restic-related and otherwise).
I’m running this tree (ie PR#2195, “out-of-order-restore-no-progress”) trying to solve that other problem, and it doesn’t seem to do anything memory-wise to restic: In fact, I’m seeing even larger memory usage. As of now, not even 15mins into the restore, it’s using over 36GB(!):
ps auwx | grep restic | grep -v grep
root 7497 100.0 54.1 40974204 36297964 s008 R+ 11:35AM 21:35.51 restic_out-of-order-restore-no-progress --verbose --target=. --include=/alex/financeiro restore 706e249a
root 7498 0.0 0.1 4485680 43192 s008 S 11:35AM 0:00.62 rclone serve restic --stdio --b2-hard-delete --drive-use-trash=false REDACTED1:restic/REDACTED2
Reading the PR, I don’t see any mention of memory optimization; my impression is that its main objective is to optimize restore speed (I guess, even at the expense of using more memory, as seen above).
Do you agree, @764287 , or am I missing something?
I have it right here (got it for restic backup as asked by @fd0, to help him with some memory usage profiles – and I’m in fact still running it for backup). No sense running it for restore, as my main issue with restores right now is time and not memory.
Cheers,
– Durval.