DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=Z5ZxZn4pbzVsWLdw5dqXbtCSdaPo
	1zNTAzVnyCy6C02StRZlK+kopdG+xrWxEL92fwZIzZmmZcFZgeW+qukSsS9Pzi2V
	KXmv4E1XpZiEXhAWBtB3F1hErXVnH9z/xzabMKMhALm3OgzdwV6+dlxRjFxmDtDX
	zX/irgXW4PVWpfQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Subject: Re: Telnet / SSH connection timeout on LAN
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <1283519593.20150709090453@yandex.ru>
Date: Fri, 10 Jul 2015 07:19:43 -0600
Message-Id: <5C24455B-3D28-4C6D-A77B-70BB5D67F0AA@etr-usa.com>
References: <1436142936994-119480.post@n5.nabble.com> <7931485F-EEA3-4C1B-8B2C-E495EF5ED1A9@etr-usa.com> <1283519593.20150709090453@yandex.ru>
To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On Jul 9, 2015, at 12:04 AM, Andrey Repin <anrdaemon@yandex.ru> wrote:
> 
>> rsync requires a pretty heavy network transaction to figure
>> out if files have changed.
> 
> I'm rsync'ing about 15 gigabytes of my home directory with just a few megs of
> network exchange.

“Just?”

That was my definition of “heavy”.

Consider all the disk I/O required.  In its default mode, rsync must do a full directory tree scan on the directory to be transferred, on *both* ends.  For each file with a different mtime or size, it must then recompute all the hashes in that file, again on both sides.

Can you really handwave away megs of network I/O and potentially gigs of disk I/O?  Do you never use locate(1) instead of find(1)?  Same issue.

On top of that, the OP wants to do this every time the machine becomes idle.  Even if it was idle a few seconds ago, did some work, and is idle again, the OP wants all this work to be done all over again.

Horribly wasteful.

I believe Dropbox and its major competitors avoid the need for this tree scan by hooking into the OS’s filesystem change notification API, so that they don’t do any network or disk I/O until one of the files it is responsible for changes.

That’s the right way.
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple