Hello John!
On Montag, 2. Juli 2007, John Peacock wrote:
> Perhaps if you described what you actually hope to accomplish (e.g. keep
> a remote filesystem in sync with a local repository), rather than a
> specific mechanism (like pipe or tar), someone could make a more
> intelligent suggestion.
Ok, here is it.
I'd like to push the contents of some repository (say, 2GB) to many (order of
several hundred) machines at once, with a granularity of, say, a day.
Believing (but not having benchmarked) that restoring file data from a
compressed repository is *much* more CPU-using than simply streaming from a
RAID array, I thought that the easy way would be to generate a tar file, and
let the clients fetch it.
Of course, I can do an export and tar that, but I wanted to ask because the
filesystem fragmentation is much lower if I don't need to do all that into a
temporary directory, and it could be done much *faster* too, if it didn't
need to write the data twice.
(Just get the data from the repos, and write a single stream, possibly even
into a raw device - which gets me easily more than 100MByte/sec transfer
rate).
> p.s. check out socat:
>
> http://www.dest-unreach.org/socat/doc/socat.html
Thank you, I already know netcat which does more or less the same.
> if you want to do something like this:
>
> svn cat /repository/path | socat [options]
Thank you, but that works only for files, not entire directory structures.
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 3 07:33:57 2007