Windows Delivery Optimization and Disk Caching Explained

Delivery Optimization is the Windows service that downloads updates from Microsoft and from other PCs on your network or the internet. It is a peer-to-peer cache, and it produces a steady mix of downloads, uploads, and local reads.

This guide explains what Delivery Optimization stores, how it behaves, and how a disk cache interacts with it.

PAGE CONTENT

• What Delivery Optimization Stores
• How the DO Cache Behaves
• How It Interacts with a Disk Cache
• Where the Two Conflict
• Configure a Cache for Delivery Optimization
• FAQs About Delivery Optimization and Caching
• Back Up Windows Before You Change Settings

What Delivery Optimization Stores

The DO cache is a temporary store, and it lives in a single hidden folder:

• The DO cache folder. Usually %WinDir%\SoftwareDistribution\DeliveryOptimization, which holds downloaded chunks and serves them to peers.
• Chunk files. Update payloads are split into chunks, each identified by a hash, so the same chunk from different sources can be deduplicated.
• Metadata files. Small databases that track which chunks belong to which update, read on every download and upload.
• The working set is tied to update cycles. The folder fills during a patch Tuesday and drains over the following days, similar to the Windows Update cache.
• Peer uploads read the cache. When another PC on your network downloads the same update, your PC reads chunks from the DO cache and sends them out, which is a read workload.

How the DO Cache Behaves

The access pattern is a mix of streaming writes and scattered reads, and the details matter:

• Downloads are streaming writes. Chunks land as fast as the network or the peer can send them, which is sequential write work.
• Peer uploads are scattered reads. Another PC requests specific chunks by hash, which are read out of order from the cache.
• The folder is temporary. Chunks are deleted once the update is installed and the peer list expires, which is the pattern a cache cannot help - see when a disk cache does not help.
• The metadata is read on every session. The small index files are touched whenever the service starts, which is a repeatable pattern.
• Writes and reads happen at the same time. A download writes while a peer upload reads, which is concurrent mixed work - the distinction is in write caching vs read caching.

How It Interacts with a Disk Cache

The two layers overlap on reads, and the interaction is limited but not zero:

• Peer uploads hit the cache. If multiple PCs on a network download the same update, the serving PC reads the same chunks repeatedly, which the cache can serve from the faster tier.
• The metadata stays in the RAM tier. Small index files are read on every service start and stay hot.
• Downloads are not cached. A chunk is written once and then either installed or uploaded, so caching it for long-term reuse is a poor bet.
• The folder is bounded by the DO limit. The cache size is configurable, and once it fills, old chunks are evicted, which is closer to a circular buffer than a cache.
• Cold installs are unaffected. The first install of an update reads the chunks from the DO cache, which is one-pass work the disk cache cannot accelerate.

Where the Two Conflict

A few setups work against each other, and they are easy to avoid:

• Caching the DO folder aggressively. A read cache learns chunks that are deleted within days, which wastes cache space that the working set could use.
• Setting the DO limit too high. A large DO cache fills the SSD with temporary chunks that crowd out real data and the cache tier itself.
• Disabling Delivery Optimization entirely. That forces every PC to download from Microsoft directly, which is slower and uses more bandwidth for no real speed gain.
• Putting the DO folder on an SMR drive. Mixed reads and writes are exactly what shingled drives cannot handle - see SMR drives explained.
• Running updates during heavy work. A download competes with builds, copies, and the cache warm-up itself for the same disk.

Quick summary

Delivery Optimization is a poor target for read caching. The wins come from leaving the DO limit modest and letting the metadata warm the cache naturally.

Configure a Cache for Delivery Optimization

The sensible setup is to leave the DO folder where it is, keep the DO limit at a few percent of the SSD, and point a disk cache at the system volume for the files you actually reopen. Qiling Fast Cache uses a RAM tier for the hottest blocks and an SSD tier for the rest, and shows the hit rate in the task list.

• Free Download
• Windows 11/10/8/7, 100% Secure

Step 1. Install Qiling Fast Cache and open the task list. Check the Delivery Optimization limit in Settings before configuring anything.

Step 2. Click the "+" button and select the system volume. The DO folder lives under C:\Windows, so the cache picks it up automatically.

Step 3. Size the SSD tier for your real working set, not for the DO folder. Chunks are temporary and should not crowd out real data.

Step 4. Run a patch Tuesday cycle, then read the hit rate - see how to check cache hit rate - and confirm that the cached data is the metadata and peer-read chunks, not the deleted download files.

FAQs About Delivery Optimization and Caching

Does Delivery Optimization slow down my PC?

Rarely. It runs in the background and mainly during update cycles, not during daily work.

Should I cache the DO folder?

Little benefit. Chunks are temporary and deleted within days, so a read cache learns files that are removed shortly after.

What should I set the DO limit to?

A few percent of the SSD is enough. A larger limit fills the drive with temporary chunks that crowd out real data.

Is it safe to disable Delivery Optimization?

Yes, but it forces every PC to download from Microsoft directly, which is slower and uses more bandwidth.

Does peer upload benefit from a disk cache?

Slightly, when multiple PCs on a network request the same chunks. The reads are scattered but repeatable.

Back Up Windows Before You Change Settings

Reconfiguring storage and cache settings is easier to undo when you have a recent image. Qiling Disk Master creates a full Windows backup you can restore from.

• Free Download
• Windows 11/10/8/7, 100% Secure

Part 1: Create a Full System Backup

Step 1. Install and open Qiling Disk Master. On the home screen, open "Backup and Recovery" and choose "System Backup". This option automatically includes Windows and the hidden boot partitions, so you do not have to select them one by one.

Step 2. Check the source. The disk where Windows is installed and its system partitions are already ticked for you. If you only need your personal documents, run a separate "File Backup" task instead.

Step 3. Click the destination box and choose where the image should be saved. Use an external HDD or SSD, a NAS, or any drive other than the one Windows is installed on, and make sure it has enough free space.

Step 4. Review the task summary and click "Proceed". Wait until the progress bar reaches 100%. Do not unplug the drive or turn off the PC while the backup is running.

Part 2: Restore Windows from the Backup

Step 1. Open Qiling Disk Master again, go to "Backup and Recovery", and select the recovery option. Your backup images are listed, so pick the one you created before the changes began.

Step 2. Choose the target disk or partition. Normally you restore to the original system disk. If the drive was replaced, select the new disk instead, and the restore rebuilds Windows together with its boot partitions.

Step 3. Preview the restore plan, click "Proceed", and confirm the warning. The PC restarts to finish the job, and Windows comes back exactly as it was on the day the image was created.

Conclusion

Delivery Optimization is a poor target for read caching because its chunks are temporary and deleted within days of an update. The wins come from leaving the DO limit modest, keeping the folder on a healthy SSD, and letting the metadata warm the cache naturally. Point a disk cache at the system volume for the files you actually reopen, size the SSD tier for your real working set rather than the DO folder, and read the hit rate after a patch Tuesday cycle rather than assuming peer uploads need special treatment.

Protect your PC with Qiling Backup—create a system image before your next round of settings changes.

For more Windows performance guides, see how shadow copies interact with a cache, the installer cache and caching, how Storage Sense interacts with a cache, Defender real-time protection and caching, and NTFS compression and caching.

Related Articles

• Windows Hibernation and Disk Caching
  Another Windows service whose cache fills and drains in cycles.
• Power Loss Protection and Disk Caching
• Thermal Throttling and Disk Caching
• Memory Compression and Disk Caching
• File Deduplication and Disk Caching

Is this information helpful?   Yes   No

This information is not relevant.

This information is not easy to understand.

This information is not deep enough.

What can we do to improve this information? (Optional)

Refresh Please enter the verification code!