From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <2bb3cd1f32813b23687084928e603243@quanstro.net> From: erik quanstrom Date: Tue, 6 Jan 2009 08:55:51 -0500 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [9fans] Changelogs & Patches? Topicbox-Message-UUID: 7a915774-ead4-11e9-9d60-3106f5b1d025 > >> I'm still trying to figure out what kind of approximation of the > >> above > >> would be possible with fossil/venti. > > > > how about making a copy? venti will coalesce duplicate blocks. > > But wouldn't you still need to send these blocks over the wire (thus > consuming bandwidth and time)? key word "approximation". ☺ assuming that not all of your tree is in cache, moving the blocks over the wire would be much faster than the disk access. assuming just gbe, you should be able to copy 50mb/s out of and back into the same venti server. how big are your snapshots that this would be a problem? i don't know enough about fossil's structure, but i think you could write a specialized. - erik