Bug 2296 - Idea: transparently uncompress .gz and .bz2 files before synchronizing.
Summary: Idea: transparently uncompress .gz and .bz2 files before synchronizing.
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 2.6.4
Hardware: All Linux
: P5 enhancement (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
Depends on:
Reported: 2005-02-01 19:17 UTC by Richard Neill
Modified: 2009-08-07 05:16 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Richard Neill 2005-02-01 19:17:29 UTC
Here's an idea that occurred to me, which I think might make a useful feature:
If one is synchronizing a .gz or.bz2 file via rsync, then this is very
inefficient. Why not transparently unpack it before synchronizing?

According to Google, this was discussed previously in 2001, but perhaps it may
be worth bringing this up again? A quick measurement I did shows that
uncompressing the file before transfer gives an improvement of a factor of 10.
[.tar.bz2 files synchronize fairly efficiently over rsync if most of the archive
contents are unaltered. However, if the archive files all contain many small
changes (e.g. a database dump), the synchronzation is little better than scp.]

Yes, I do know that the real solution is not to use rsync to transfer compressed
files in the first place. So this is just a nice idea (to transparently do the
most obvious thing) rather than a suggestion of great importance.

Thanks very much,

Comment 1 Wayne Davison 2005-02-12 14:44:03 UTC
I'm not that enamored with this idea, but I'll leave this open as a place-holder
for future consideration.
Comment 2 roland 2009-08-07 05:16:06 UTC
you may have a look at patches/source-filter_dest-filter.diff