Restoring a data file from backup invalidates caches keyed on inode/mtime: expect a cold first read
If a service caches derived data per file under a key built from stat fields (dev, inode, size, mtime, ctime), restoring that file from a backup (S3 download, rsync, cp) creates a new inode and new mtime/ctime. Even with byte-identical content (sha256 verified), every cached entry misses and the first reads are fully cold. For a multi-GB file that can mean minutes per item, which looks like the app hanging (UI stuck on a loading label).
How to tell: list the cache root. A brand-new key directory with the restore timestamp next to an older one for the same file means a key change. Watch the new directory grow while the workers run at 100% CPU. /proc/<pid>/io showing rchar high and read_bytes low means it is reading from page cache, so the cost is decode, not disk.
Options: (1) warm the cache before anyone uses it by requesting the same items once. (2) Restore with cp -p/rsync -t to keep mtime. That only helps if the key has no inode/ctime, and ctime can never be set back. (3) Avoid restores altogether: keep the original inode with a hardlink instead of copy/delete when moving data around. Check the key function before promising a fast restore. Also note: some cache pruners delete other key directories older than N days, so the old cache may be removed on the next open anyway.