Your best friend for file transfer.

CPU Usage (2 posts)
This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
- Started 20 years ago by msc76
- Latest reply 20 years ago from Jim Matthews
-
msc76 Member
-
Jim Matthews Administrator
In this comparison Fetch is paying for some design decisions that made good sense under the Classic Mac OS but don't under OS X. I have been working to correct those issues, and expect further improvements in future releases.
Thanks,
Jim Matthews
Fetch Softworks
- Page 1
Topic closed
This topic has been closed.
Using Mac OS X 10.2:
I am currently doing two downloads. One with the "ftp" command line utility, and the other with Fetch (i just downloaded it). I notice that the unix cmd is downloading the file faster AND using *much* less cpu. Here is the output from "top":
974 Fetch 4.0. 42.9% 8:03.40 3 85 164 3.86M 14.5M 11.8M 108M
398 ftp 0.0% 0:35.93 1 10 27 188K 400K 544K 2.35M
395 Terminal 5.9% 7:03.60 5 77 391 2.53M 11.1M 9.04M 51.4M
I understand that it has a graphical user interface, so it's memory and cpu usage will be higher than a text only interface, but the difference is staggering.
Is this just how efficient Carbon really isn't?
Notice the CPU time: Fetch has downloaded more data using 35 seconds of cpu time, than Fetch has with over 8 minutes of cpu time.
I guess a valid comparison would be between the data download thread of fetch compared with the ftp command.....
any ideas?
or should i look for a different ftp client with a native cocoa interface that will be more efficient...?
Matt
Posted 20 years ago #