Maybe someone can explain this away, but when I run setiathome on my Mac OS X Server the network throughput drops from 80+MB/s to as little as 1.2MB/s. The processes are niced at 19, but as soon as I kill them the throughput jumps. This can be measured using SMB, AFP, or even scp...

Sometimes when running BOINC on my MacBook Pro at 100%, my ethernet (wired) connection fails. My assumption is that the heat from the CPUs causes the failure, but it could be something else. I do not have this issue when I connect with USB WiFi or AirPort. After a reboot, the wired connection is restored.

---

I have two machines, a Dual G5 @ 2.7 GHz and a MacBook @ 2.2 GHZ. I haven;t had any ethernet failures or anything like that. But the throughput on basic network up/down load is generally half of normal when BOINC is running. Both processors in each machine indicate that they are maxed out at 100%.

Beside BOINC, I am using the optimized G5 and Intel MultiBeam apps. I have sort of accepted that this is what happens while crunching. It would be nice to get the network performance back.

Maybe someone can explain this away, but when I run setiathome on my Mac OS X Server the network throughput drops from 80+MB/s to as little as 1.2MB/s. The processes are niced at 19, but as soon as I kill them the throughput jumps. This can be measured using SMB, AFP, or even scp...

Have you tried setting your CPU utilization to 90% or less in the SETI@home preferences? I would assume that the network daemon(s) is(are)n't getting enough cycles to run network communications at full speed.

---