# Compare about backup sizes of different versions?
**URL:** https://forum.duplicati.com/t/compare-about-backup-sizes-of-different-versions/18029
**Category:** Features
**Created:** [June 2, 2024, 3:49pm UTC](https://forum.duplicati.com/t/compare-about-backup-sizes-of-different-versions/18029 "2024-06-02T15:49:30Z")
**Posts on this page:** 1
**Showing post:** 5
### Author:  [@ts678](https://forum.duplicati.com/u/ts678)
#### Post date: [June 4, 2024, 11:29am UTC](https://forum.duplicati.com/t/compare-about-backup-sizes-of-different-versions/18029/5 "2024-06-04T11:29:02Z")
> [@vbs](#):
>
> Hm, a possibly (?!) easy to add information in the backup result report would be to have `uploadedBytes` for every file separately?
The value is from a section:
```plaintext
"BackendStatistics": {
"RemoteCalls": 29,
"BytesUploaded": 112855294,
```
which deals with Destination files. I don’t think it has Source file details. There might be a similar issue gathering statistics earlier in the processing, but I’m not certain. If you look at [Channel Pipeline](https://forum.duplicati.com/t/channel-pipeline/11466/4), it has a number of processing steps, and what one would like would be one that knows each file path, and also added (not currently in backup) blocks resulting from the file path. I don’t think (not sure) that this exists.
Better developer documentation would be nice, but the last time I looked, I thought main backup path is:
> FileEnumerationProcess.cs → SourcePaths → MetadataPreProcess.cs → ProcessedFiles → FilePreFilterProcess.cs → AcceptedChangedFile → FileBlockProcessor.cs → StreamBlock → StreamBlockSplitter.cs → OutputBlocks → DataBlockProcessor.cs → BackendRequest
which shows how BackendStatistics is pretty far removed from file paths. I think DataBlockProcessor.cs
>
is the first spot that knows which blocks are new, and at this time it’s just blocks. Does it still know path?
>
looks like “no” to me, but an expert developer (they are rare, which limits ability to add features) may differ.
> [@vbs](#):
>
> I would like to know if I could optimize the backup size by possibly easy measures.
One easy way to reduce backup size is to backup fewer folders and files, e.g. based on a Source analysis, using any number of easily available tools. This works worse if you have a lot of exclusions they don’t know. Duplicati’s reports can find big files after excludes, but they’re not very good at adding up total of small files.
Until you run [The PURGE command](https://docs.duplicati.com/en/latest/04-using-duplicati-from-the-command-line/#the-purge-command), versions still retained will hold whatever files they originally backed up.
> [@Find large files in backup?](https://forum.duplicati.com/t/find-large-files-in-backup/7256):
>
> Hello! Is it possible to use the FIND command to discover large files that are a part of my previous backup(s)? Context: In order to save on storage costs, I’d like to manually PURGE some large files that I no longer need from previous backups. In most cases, though, I don’t know what the files are in advance - they could be ones that I deleted from my source disk at some point and no longer remember. I don’t want to impose a hard limit on the filesize (i.e. --skip-files-larger-than) because b…
> [@Visualize backup data usage](https://forum.duplicati.com/t/visualize-backup-data-usage/6691):
>
> Since Duplicati is cataloging everything, it would be really helpful if it could show me how much space each directory and file in the data is contributing to the size of my backups. My current source data set is over 35GB, and I could probably trim it quite a bit if only I could easily tell what some of the bigger contributors are.
---
_[View the full topic](https://forum.duplicati.com/t/compare-about-backup-sizes-of-different-versions/18029)._