<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: File managers, parallel copy, and performance hits</title>
	<atom:link href="http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/feed/" rel="self" type="application/rss+xml" />
	<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/</link>
	<description>I like stuff, and you're reading about it</description>
	<lastBuildDate>Thu, 08 Apr 2010 07:39:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-94</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 26 Apr 2009 07:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-94</guid>
		<description>CLI FTW.

This may be the fail approach but you could always type while &#039;cp&#039; is copying, hit enter, and as long as the program doesn&#039;t require any further input your command will be run once the previous is finished.

You could also use &#039;at&#039; and have your second copy command run around when the first one should be complete. It may not be perfect but its more efficient then copying two files at once and requires no baby sitting.</description>
		<content:encoded><![CDATA[<p>CLI FTW.</p>
<p>This may be the fail approach but you could always type while &#8216;cp&#8217; is copying, hit enter, and as long as the program doesn&#8217;t require any further input your command will be run once the previous is finished.</p>
<p>You could also use &#8216;at&#8217; and have your second copy command run around when the first one should be complete. It may not be perfect but its more efficient then copying two files at once and requires no baby sitting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-89</link>
		<dc:creator>J</dc:creator>
		<pubDate>Mon, 23 Mar 2009 13:15:56 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-89</guid>
		<description>I just have a batch on my desktop called copy.cmd

It uses robocopy (free from Microsoft).  On Linux/BSD/unix I have one called copy.sh which uses rsync

I just edit the file, plug in the info and double click.  Robocopy is pretty nice.

@echo off

set SRC=&quot;D:\DVD&quot;
set DEST=&quot;\\fire2\public\dvds&quot;

robocopy2k3.exe %SRC% %DEST% /E /R:5 /W:1 /X /V /Z /ETA /XN /XO</description>
		<content:encoded><![CDATA[<p>I just have a batch on my desktop called copy.cmd</p>
<p>It uses robocopy (free from Microsoft).  On Linux/BSD/unix I have one called copy.sh which uses rsync</p>
<p>I just edit the file, plug in the info and double click.  Robocopy is pretty nice.</p>
<p>@echo off</p>
<p>set SRC=&#8221;D:\DVD&#8221;<br />
set DEST=&#8221;\\fire2\public\dvds&#8221;</p>
<p>robocopy2k3.exe %SRC% %DEST% /E /R:5 /W:1 /X /V /Z /ETA /XN /XO</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: krs</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-88</link>
		<dc:creator>krs</dc:creator>
		<pubDate>Mon, 23 Mar 2009 07:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-88</guid>
		<description>@11, this is and has been a part of Gnome which ububtu uses for quite some time.</description>
		<content:encoded><![CDATA[<p>@11, this is and has been a part of Gnome which ububtu uses for quite some time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Billy O'Smithwickhamshirefordglengarry</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-87</link>
		<dc:creator>Billy O'Smithwickhamshirefordglengarry</dc:creator>
		<pubDate>Mon, 23 Mar 2009 05:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-87</guid>
		<description>WHAT</description>
		<content:encoded><![CDATA[<p>WHAT</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SJS</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-86</link>
		<dc:creator>SJS</dc:creator>
		<pubDate>Mon, 23 Mar 2009 00:13:55 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-86</guid>
		<description>Gah... the CLI solution is terrible, and doesn&#039;t deal with the situation described. The first file copy has already started... you could ^C the copy and start over (not a terrible option if using rsync, I suppose, or ^Z the copy and then use &quot;bg&quot; to continue it in the background, and start a new copy, or you can just type ahead and when the shell finishes the first copy, it&#039;ll run the command(s) you&#039;ve typed.

But as &quot;modern&quot; has been specified, you&#039;re presumably using a &#039;modern&#039; OS, which means that your OS will have buffers, and much of the writing to the external drive will merely fill the disk buffers in the OS, and the OS will (as pointed out above) automatically figure out the best way to write the data to disk -- which doesn&#039;t really matter anyway unless you&#039;ve partitioned your external disk into multiple partitions.

It&#039;s more important to queue network downloads than disk writes.</description>
		<content:encoded><![CDATA[<p>Gah&#8230; the CLI solution is terrible, and doesn&#8217;t deal with the situation described. The first file copy has already started&#8230; you could ^C the copy and start over (not a terrible option if using rsync, I suppose, or ^Z the copy and then use &#8220;bg&#8221; to continue it in the background, and start a new copy, or you can just type ahead and when the shell finishes the first copy, it&#8217;ll run the command(s) you&#8217;ve typed.</p>
<p>But as &#8220;modern&#8221; has been specified, you&#8217;re presumably using a &#8216;modern&#8217; OS, which means that your OS will have buffers, and much of the writing to the external drive will merely fill the disk buffers in the OS, and the OS will (as pointed out above) automatically figure out the best way to write the data to disk &#8212; which doesn&#8217;t really matter anyway unless you&#8217;ve partitioned your external disk into multiple partitions.</p>
<p>It&#8217;s more important to queue network downloads than disk writes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-84</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sun, 22 Mar 2009 17:55:40 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-84</guid>
		<description>I&#039;m guessing you&#039;re using either MacOS or Windows - or you&#039;re a non CLI linux user because the solution on the command line in Linux is simple:

for i in {file1,file2}; do cp $i /path/to/usb/drive/$i; done

which will do them sequentially be default as the second call to cp won&#039;t be called until the first has complete.

You could argue that you specified you were using a GUI file manager, but I would counter that you should be choosing the right tool for the job.</description>
		<content:encoded><![CDATA[<p>I&#8217;m guessing you&#8217;re using either MacOS or Windows &#8211; or you&#8217;re a non CLI linux user because the solution on the command line in Linux is simple:</p>
<p>for i in {file1,file2}; do cp $i /path/to/usb/drive/$i; done</p>
<p>which will do them sequentially be default as the second call to cp won&#8217;t be called until the first has complete.</p>
<p>You could argue that you specified you were using a GUI file manager, but I would counter that you should be choosing the right tool for the job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby Champion</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-83</link>
		<dc:creator>Toby Champion</dc:creator>
		<pubDate>Sun, 22 Mar 2009 17:13:43 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-83</guid>
		<description>Reminds me of doing the laundry. I put clothes in the washing machine, then I have to pop back half an hour later to switch them to the dryer. The attendant can do it, though, if I pay her a little.</description>
		<content:encoded><![CDATA[<p>Reminds me of doing the laundry. I put clothes in the washing machine, then I have to pop back half an hour later to switch them to the dryer. The attendant can do it, though, if I pay her a little.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Keeble</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-82</link>
		<dc:creator>Paul Keeble</dc:creator>
		<pubDate>Sun, 22 Mar 2009 16:48:28 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-82</guid>
		<description>With a few large files the difference of copying in parallel is going to be fairly minimal. The operating system will buffer up large writes and the disk will reorder the writes. Sure it might go a few percentage points faster but its not worth the more complex file manager which would confuse the users when the copies did not happen as they expected.</description>
		<content:encoded><![CDATA[<p>With a few large files the difference of copying in parallel is going to be fairly minimal. The operating system will buffer up large writes and the disk will reorder the writes. Sure it might go a few percentage points faster but its not worth the more complex file manager which would confuse the users when the copies did not happen as they expected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paschal</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-81</link>
		<dc:creator>Paschal</dc:creator>
		<pubDate>Sun, 22 Mar 2009 15:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-81</guid>
		<description>The idea queued actions already exists in Filezilla (an FTP client, a filemanager of sorts I guess). I guess the scenarios you describe (i.e. high latency copy) is more common in FTP land.</description>
		<content:encoded><![CDATA[<p>The idea queued actions already exists in Filezilla (an FTP client, a filemanager of sorts I guess). I guess the scenarios you describe (i.e. high latency copy) is more common in FTP land.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chmunk</title>
		<link>http://fitzsimmons.ca/file-managers-parallel-copy-and-performace-hits/comment-page-1/#comment-80</link>
		<dc:creator>Chmunk</dc:creator>
		<pubDate>Sun, 22 Mar 2009 14:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://fitzsimmons.ca/?p=50#comment-80</guid>
		<description>http://www.codesector.com/teracopy.php</description>
		<content:encoded><![CDATA[<p><a href="http://www.codesector.com/teracopy.php" rel="nofollow">http://www.codesector.com/teracopy.php</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
