Lab 01 · Performance

30 MB of cache for 233 thousand files, and deleting it cost nothing

Date: Oct 14, 2026Server: cPanel test server, CentOS 7, 1 accountReading time: 2 minTopic: Performance
The question

The backup runs on the same server as the sites, and every megabyte it keeps on disk is space the customer doesn’t get. How much space does the backup engine’s local cache take per account, and what happens if it is deleted?

Result
~30 MBof cache for 233,612 files, about 130 bytes per file
18 sfor an incremental run with the cache deleted, versus 19 s with a full cache; with no cache at all, 76 s

Why it matters to whoever runs the server

  • Server disk: 30 MB of cache for 233 thousand files is little next to an account of several GB. And since the cache is deleted when each account finishes, the server doesn’t pile up caches for hundreds of accounts.
  • Time: deleting the cache didn’t slow the incremental down (18 s with it deleted, 19 s with it full). No cache at all makes the backup 4× slower (76 s): a longer backup window, with the sites sharing the server for longer.
Incremental backup time for one account233,612 files, 5.7 GB · lower is better
Full cache
19 s
Cache deleted first
18 s
No cache
76 s
Source: Salvo Lab · cPanel test server · Oct 14, 2026
See the data as a table
RunTimePeak memory
First backup, empty repository53 s842 MB
Incremental, full cache19 s168 MB
Incremental, cache deleted first18 s169 MB
Incremental, no cache76 s133 MB

Method

A cPanel test server (CentOS 7, 18 cores, internal network to the storage) and one account with 233,612 files and 5.7 GB, in its own repository.

Salvo engine, writing over SFTP, with encrypted data.

Low priority (nice -n 19, ionice -c3); the test would stop on its own if server load went above 9.

What we decided

The cache is now temporary: it is created when an account’s backup starts and deleted when it ends, and the server only keeps cache for the accounts being backed up at that moment (implemented on Oct 15, 2026, running on test servers). Running with no cache at all is not worth it: the backup becomes four times slower.

?
What we don’t know yetIn the incremental runs the files were already in system memory (the Linux page cache). A real next-day backup, before dawn and with an empty cache, was measured later: 4 s for 21 thousand files (Lab 12). And this was a single account: memory with several accounts in parallel was measured in Lab 08.
Want to see Salvo on your server?Join the beta waitlist. We’ll let you know when there’s a spot.

How it connects to the other labs

Faster backups
3×The limit was the encryption, not the network: switching ciphers tripled the uploadLab 06 · Oct 15, 20268 msCompression is the costliest step of the backup; encryption barely registersLab 07 · Oct 15, 2026141The engine uploads 141 MB/s reading one file per core; 4 accounts together used 2.4 GB of memoryLab 08 · Oct 15, 202633 s3 full cPanel accounts in 33 s on a production server; the incremental, in 7 sLab 09 · Oct 15, 20264 sThe next-day backup, before dawn and cold: 4 s for 21 thousand filesLab 12 · Oct 16, 20267.7×The next-day backup on the same 6 accounts: 494 s on JetBackup, 64 s on SalvoLab 13 · Oct 16, 2026166×The first backup side by side: 45% less time and 166× fewer files on the storageLab 14 · Oct 16, 202699.98%WordPress backup with email: 6 real sites restored by Salvo and by JetBackupLab 23 · Oct 19, 2026
salvo. Backup for hosting servers. A GK2 product.
Product
Lab
Salvo
Language
© 2026 GK2We use analytics cookies (Google Analytics).salvobackup.com/lab/30-mb-of-cache-for-233-thousand-files/