Yes, I know, I should use FSCopyObjectAsync(). Anyway, my mistake, I copied the file twice, so copyItemAtPath took double time. Now I fixed my code and copyItemAtPath takes almost the same time as the Finder takes. Cool.
Regards -- Leonardo > Da: Mike Abdullah <cocoa...@mikeabdullah.net> > Data: Wed, 19 Jan 2011 23:15:13 +0000 > A: Leonardo <mac.iphone....@gmail.com> > Cc: <cocoa-dev@lists.apple.com> > Oggetto: Re: copyItemAtPath takes double time than the Finder > > Well you shouldn't be using this synchronous API for long-running copy > operations, since it can't be cancelled or give progress. > > Instead use FSCopyObjectAsync(). > > On 19 Jan 2011, at 21:42, Leonardo wrote: > >> Hi, >> I have checked, the Finder, takes only 7 seconds to copy a 500MB dmg file. >> The copyItemAtPath API takes 18 seconds to copy the same file. >> Why? Is a way to make copyItemAtPath run at the same Finder speed? >> If not, which API should I use to get the same performance? >> >> I use: >> [[NSFileManager defaultManager] copyItemAtPath:src toPath:dst >> error:&err]; >> >> Architectures: ppc, i386 >> Base SDK: Mac OS X 10.5 >> Valid Architectures: i386 ppc ppc64 ppc7400 ppc970 x86_64 >> C/C++ Compiler Version: GCC 4.2 >> Optimization Level: Fastest [-O3] >> >> >> Regards >> -- Leonardo >> >> >> _______________________________________________ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/cocoa-dev/cocoadev%40mikeabdullah.net >> >> This email sent to cocoa...@mikeabdullah.net > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com