I run radio streams on my home system and whenever there is a boinc download or upload it causes the stream to dropout ...

I have set in my general preference for a maximum download rate of 5KB/s, yet download's are coming in at 20KB/s on two treads meaning my DSL connection is saturated whenever boinc needs to get work units?

Clearly this hasn't been implemented yet or if it has there is a bug.

I'm using 5.4.11 client running seti, rosetta, einstein

---

Well I've change my max download rate down and up to 1Kbs and it still didn't work. I then looked on rosetta site and found the following post .. http://boinc.bakerlab.org/rosetta/forum_thread.php?id=467

I've now set my network preferences from always on to run based on preferences .. hopefully it will obey the total bandwidth settings I have put in place.

---

nope .. still downloading at 20Kbs+ even though I've used the boinc limitation to 1Kbs.

Anyone know why this doesn't work? Anyone actually care?

---

Did you update BOINC after you changed the preferences?

---

Did you update BOINC after you changed the preferences?

Yup .. I'm using BAM set to update once an hour. Checked relevent xml file.. Here's my global pref's

<global_preferences>
<source_project>http://bam.boincstats.com/</source_project>
<mod_time>1158639159</mod_time>
<cpu_scheduling_period_minutes>44</cpu_scheduling_period_minutes>
<idle_time_to_run>1</idle_time_to_run>
<work_buf_min_days>0.3300000</work_buf_min_days>
<max_cpus>32</max_cpus>
<disk_interval>60</disk_interval>
<disk_max_used_gb>100.0</disk_max_used_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_min_free_gb>1.5</disk_min_free_gb>
<vm_max_used_pct>75</vm_max_used_pct>
<max_bytes_sec_down>1000</max_bytes_sec_down>
<max_bytes_sec_up>1000</max_bytes_sec_up>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<run_if_user_active/>
<leave_apps_in_memory/>
<hangup_if_dialed/>
<venue name="global">
<cpu_scheduling_period_minutes>44</cpu_scheduling_period_minutes>
<idle_time_to_run>3</idle_time_to_run>
<work_buf_min_days>0.3300000</work_buf_min_days>
<max_cpus>64</max_cpus>
<disk_interval>60</disk_interval>
<disk_max_used_gb>100.0</disk_max_used_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_min_free_gb>1.5</disk_min_free_gb>
<vm_max_used_pct>75</vm_max_used_pct>
<max_bytes_sec_down>1000</max_bytes_sec_down>
<max_bytes_sec_up>1000</max_bytes_sec_up>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<run_if_user_active/>
<leave_apps_in_memory/>
<hangup_if_dialed/>
</venue>
</global_preferences>

---

I'm pretty darn sure that the upload/download speeds is controlled by the server side...... Found that some projects stick to the number, some register it just since its in the default profile options and blast u with whatever the server has to spare.

That being the case it should be documented in there FAQ that they don't actually honour bandwidth settings. What version of the server software do projects have to be on to actually honour correct settings, and if they don't intend on honouring it shouldn't these options be greyed out?

---

Still no satisfaction on this issue .. is anyone actually reading this?

Here is my current golbal_prefs.xml - as you will note all have <max_bytes_sec_down> set at the minumin level allowed being 1000. All my clients aren't obeying this setting which are now on 5.6.4.

Anyone know why this isn't working?

<global_preferences>
<source_project>http://bam.boincstats.com/</source_project>
<mod_time>1159064013</mod_time>
<cpu_scheduling_period_minutes>37</cpu_scheduling_period_minutes>
<idle_time_to_run>3</idle_time_to_run>
<work_buf_min_days>0.4500000</work_buf_min_days>
<max_cpus>2</max_cpus>
<disk_interval>60</disk_interval>
<disk_max_used_gb>100.0</disk_max_used_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_min_free_gb>1.5</disk_min_free_gb>
<vm_max_used_pct>75</vm_max_used_pct>
<max_bytes_sec_down>1000</max_bytes_sec_down>
<max_bytes_sec_up>1000</max_bytes_sec_up>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<run_if_user_active/>
<leave_apps_in_memory/>
<hangup_if_dialed/>
<venue name="home">
<cpu_scheduling_period_minutes>7</cpu_scheduling_period_minutes>
<idle_time_to_run>3</idle_time_to_run>
<work_buf_min_days>0.6600000</work_buf_min_days>
<max_cpus>32</max_cpus>
<disk_interval>60</disk_interval>
<disk_max_used_gb>100.0</disk_max_used_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_min_free_gb>1.5</disk_min_free_gb>
<vm_max_used_pct>75</vm_max_used_pct>
<max_bytes_sec_down>1000</max_bytes_sec_down>
<max_bytes_sec_up>1000</max_bytes_sec_up>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<run_if_user_active/>
<leave_apps_in_memory/>
<hangup_if_dialed/>
</venue>
<venue name="work">
<cpu_scheduling_period_minutes>15</cpu_scheduling_period_minutes>
<idle_time_to_run>3</idle_time_to_run>
<work_buf_min_days>0.5500000</work_buf_min_days>
<max_cpus>64</max_cpus>
<disk_interval>60</disk_interval>
<disk_max_used_gb>100.0</disk_max_used_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_min_free_gb>1.5</disk_min_free_gb>
<vm_max_used_pct>75</vm_max_used_pct>
<max_bytes_sec_down>1000</max_bytes_sec_down>
<max_bytes_sec_up>1000</max_bytes_sec_up>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<run_if_user_active/>
<leave_apps_in_memory/>
<hangup_if_dialed/>
</venue>
</global_preferences>

---

I got this answer from Dr. Anderson:

The "max network bandwidth" preference is not enforced by the client since version 5.0.

However, I think the 5.6 client will enforce this preference.

-- David

---

Please test your flavour of BOINC 5.6.5 which should enforce the download/upload speeds again.

And please report here if it work alright. Or not. :)

The version is a reasonable stable ALPHA version. Please report any problems you have with it, on what operating system and what else you were doing at the time.
Please also report on what CPU/RAM/HDD package you ran it.

---

Please test your flavour of BOINC 5.6.5 which should enforce the download/upload speeds again.

And please report here if it work alright. Or not. :)

The version is a reasonable stable ALPHA version. Please report any problems you have with it, on what operating system and what else you were doing at the time.
Please also report on what CPU/RAM/HDD package you ran it.

Being a new Alpha tester I've already verified that 5.6.5 has indeed fixed up this issue, having relpied to the list. Happy days indeed to have Boinc working as one would assume it should based on what the preferences lead one to believe.

---