On 8/18/2006 1:42 PM, Norman Palardy wrote: > > On Aug 18, 2006, at 11:33 AM, Charles Calvert wrote: > >> I am curious about it, though. Is there enough non-io overhead in >> FolderItem.CopyFileTo that a significant improvement is possible? > > There seems to be.
Interesting. I read an old thread in the archives discussing this and the difference seems to vary with the performance of the drive. That makes sense. > And, since it is a thread of your own design it's possible to get some > feed back on how much has been copied; something not possible with > CopyFileTo. Sorry, but I thought you were suggesting that I use CopyFileTo to copy individual files inside my worker thread. Do you mean that I can get feedback because I'm using separate threads (and thus can push progress info back to the GUI via events, etc.) or because I would replace CopyFileTo with an API call? >> Even with the overhead of divvying up the files to the threads and making >> sure they don't step on each other? > > Yes. > I have a single process create the required folder hierarchy, then a > number of threads to do the file copies into that hierarchy. Interesting idea. Thanks, -- Charles Calvert Celtic Wolf, Inc. (703) 580-0210 [EMAIL PROTECTED] http://www.celticwolf.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
