Your best friend for file transfer.
Fetch
Is performance a problem for you? (3 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 22 years ago by jtrascap
- Latest reply 22 years ago from Jim Matthews
-
jtrascap Member
-
jtrascap Member
I hate replying to my own post, but I should mention that it sucks down the system on nearly all functions, not just on a system connect.
On what I'm using:
- new Dual-USB iBook 600Mhz
- 640MBs RAM
- 30GB drive
- OSX 10.1.1.2
- Apache/FTP/Telnet running
- Firewall up and configurednothing special...
-
Jim Matthews Administrator
Yes, I'm hard at work on Fetch 4.0.2, and one of the areas I'm addressing is CPU usage on OS X. The rules are quite a bit different on X, and that wasn't reflected in 4.0 and 4.0.1, so there's plenty of room for improvement.
Thanks for the feedback,
Jim Matthews
Fetch Softworks
- Page 1
Topic closed
This topic has been closed.
I'm using 4.01and I can't believe how much of the system Fetch pulls down trying to connect. It's routine to see it use 55-70% of the system tryingv to connect! The entire system get sluggish running Fetch.
Annoying. Really annoying. I allowed it when the system was new and 4.01 was just released. I registered Fetch within days of the release, primarily as a payback for years of fast and fruitful 3.x usage, but I'm really annoyed with the terrible performance and the virtually-nil updates of the app.
When I can't believe how unresponsive Fetch is with a particular website, I will occasionally run a competing product and pop open a terminal running "top".
I've yet to see that "other product" rise above 17% - it usually bounces between 10 and 15%.
PLEASE tell me that Fetch is being optimized as we speak. I'm ready to drop it by the roadside and recommend others to the competing product. Fetch was fabulous previously - I'd love to be able to recommend it again...
Posted 22 years ago #