For some reason, phpBB won't let Tea post. This, in my opinion, is a very good thing. She ge's the "you can't make another post so soon" error message even though she hasn't posted anything in this session yet.)
But she asked me to post the following on her behalf:
-----------------------
I'm still experimenting, Clocker, trying to find the best method. At present I am leaning toward having either 3 or 4 processes on each machine of Athlon 1200 class or better, two for, say, a Duron 750 or a P-III, and just the one on the K6-IIIs (which make very little contribution anyway).
I'm just letting the processes run continually. I have no idea what overheads are involved in the task-switching. Am I loosing efficiency by having copy #1 switch to copy #2 to #3 and back all the time? In the end, it doesn't matter: if I run a single process on a fast machine, it will have finished long before it gets a net connection again, and the efficiency loss there is huge.
At home (two machines) I connect twice a day - morning and evening. At work, I'm usually connected more-or-less all day from 11ish till 5 or 6. (Except weekends.) Sometimes (like today) I stay late and have tea at the office, which means the office machines get an extra connect-time bonus, but the home machines (of course) suffer instead.
How are the others among us who are on dial-up coping with F@H?
Any hints, tips or strategies to share?