Hi! Me again.
I’m trying to restore ~230G archive file from repository served by rest-server.
Today I looked at our Grafana and found in I/O panel that network and disk usage had saw-like graphs while running
restic restore. In the picture below looks like restic downloads some data, saturates network connection while keeping block write low, after some time (~40s) network usage drops, and restic performs write to disk, causing block i/o spike in graphs.
The question is: is this usual behavior? Does that reflects restoration algorithm?
UPD: Restic built from master, commit 58bd165253a429f93fe9b262dc8a19fc90716a6a