Travis and I hammered out a small issue, things seem to be running very smoothly now.

-Matthew

Thanks God Matthew... let us keep crunching please! We have some ATI babies that needs to crunch!

Best Regards!

Travis and I hammered out a small issue, things seem to be running very smoothly now.

-Matthew

Thanks God Matthew... let us keep crunching please! We have some ATI babies that needs to crunch!

Best Regards!

Works great for 1 day... receiving right now :

3/4/2011 8:31:17 AM Milkyway@home Reporting 1 completed tasks, requesting new tasks for GPU
3/4/2011 8:31:20 AM Milkyway@home Scheduler request completed: got 0 new tasks
3/4/2011 8:31:20 AM Milkyway@home Message from server: (Project has no jobs available)

My GPU is running out of WU... again... =(

Regards!

not getting any...

6/03/2011 10:05:41 AM | Milkyway@home | Sending scheduler request: Requested by user.
6/03/2011 10:05:41 AM | Milkyway@home | Requesting new tasks for ATI GPU
6/03/2011 10:05:46 AM | Milkyway@home | Scheduler request completed: got 0 new tasks
6/03/2011 10:05:46 AM | Milkyway@home | No work sent
6/03/2011 10:05:46 AM | Milkyway@home | Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

[edit]
Good news!

6/03/2011 10:11:23 AM | Milkyway@home | Sending scheduler request: To fetch work.
6/03/2011 10:11:23 AM | Milkyway@home | Reporting 2 completed tasks, requesting new tasks for ATI GPU
6/03/2011 10:11:30 AM | Milkyway@home | Scheduler request completed: got 15 new tasks

not getting any GPU work units.
3/8/2011 8:21:10 PM Milkyway@home Scheduler request completed: got 0 new tasks
3/8/2011 8:21:10 PM Milkyway@home Message from server: No work sent
3/8/2011 8:21:26 PM Milkyway@home Computation for task de_separation_19_3s_fix_4_2060697_1299638139_0 finished
3/8/2011 8:22:20 PM Milkyway@home Sending scheduler request: To fetch work.
3/8/2011 8:22:20 PM Milkyway@home Reporting 1 completed tasks, requesting new tasks for GPU
3/8/2011 8:22:22 PM Milkyway@home Scheduler request completed: got 0 new tasks
3/8/2011 8:22:22 PM Milkyway@home Message from server: No work sent
3/8/2011 8:23:32 PM Milkyway@home Sending scheduler request: To fetch work.
3/8/2011 8:23:32 PM Milkyway@home Requesting new tasks for GPU
3/8/2011 8:23:34 PM Milkyway@home Scheduler request completed: got 0 new tasks
3/8/2011 8:23:34 PM Milkyway@home Message from server: No work sent
3/8/2011 8:25:44 PM Milkyway@home Sending scheduler request: To fetch work.
3/8/2011 8:25:44 PM Milkyway@home Requesting new tasks for GPU
3/8/2011 8:25:46 PM Milkyway@home Scheduler request completed: got 0 new tasks
3/8/2011 8:25:46 PM Milkyway@home Message from server: No work sent
3/8/2011 8:27:56 PM Milkyway@home Sending scheduler request: To fetch work.
3/8/2011 8:27:56 PM Milkyway@home Requesting new tasks for GPU
3/8/2011 8:27:58 PM Milkyway@home Scheduler request completed: got 0 new tasks
3/8/2011 8:27:58 PM Milkyway@home Message from server: No work sent
3/8/2011 8:34:03 PM Milkyway@home Sending scheduler request: To fetch work.
3/8/2011 8:34:03 PM Milkyway@home Requesting new tasks for GPU
3/8/2011 8:34:05 PM Milkyway@home Scheduler request completed: got 0 new tasks
3/8/2011 8:34:05 PM Milkyway@home Message from server: No work sent

I have bought a HD4850 from the secondhand market (45 Euro) and brought it online 2 days ago.
Collatz did work fine from the beginning. From Milkyway I was a little bit disappointed for the little cache. I had to make an update request every half an hour. This was not practicable for a system which is 7/24 online.

But from today morning (MEZ) there is every 2 minutes :) an automatic update request and the system gets enough work. The turnaround time is now 0.03 Days.
If this behavior continues I would be satisfied. :)
My question: Was there a change on the server, or depends the interval of the requests on the individual statistic of my machine?

Settings:
BOINC Manager V 6.12.15

<global_preferences>
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<suspend_cpu_usage>0.000000</suspend_cpu_usage>
<start_hour>0.000000</start_hour>
<end_hour>0.000000</end_hour>
<net_start_hour>0.000000</net_start_hour>
<net_end_hour>0.000000</net_end_hour>
<leave_apps_in_memory>0</leave_apps_in_memory>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<dont_verify_images>0</dont_verify_images>
<work_buf_min_days>0.000000</work_buf_min_days>
<work_buf_additional_days>0.500000</work_buf_additional_days>
<max_ncpus_pct>100.000000</max_ncpus_pct>
<cpu_scheduling_period_minutes>15.000000</cpu_scheduling_period_minutes>
<disk_interval>60.000000</disk_interval>
<disk_max_used_gb>10.000000</disk_max_used_gb>
<disk_max_used_pct>50.000000</disk_max_used_pct>
<disk_min_free_gb>0.100000</disk_min_free_gb>
<vm_max_used_pct>75.000000</vm_max_used_pct>
<ram_max_used_busy_pct>50.000000</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90.000000</ram_max_used_idle_pct>
<max_bytes_sec_up>0.000000</max_bytes_sec_up>
<max_bytes_sec_down>0.000000</max_bytes_sec_down>
<cpu_usage_limit>25.000000</cpu_usage_limit>
<daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
</global_preferences>

But from today morning (MEZ) there is every 2 minutes :) an automatic update request and the system gets enough work. The turnaround time is now 0.03 Days.
If this behavior continues I would be satisfied. :)
My question: Was there a change on the server, or depends the interval of the requests on the individual statistic of my machine?

Hi,

You are using a test version of BOINC manager V 6.12.15 which may be an issue.
However when running a few hours the statistics of your result do indeed matter and is anticipated. So you see MW runs smoothly.

By the way this is not a good thread for your question as it is for as the servers give no new work. And you get plenty of work...

---

Greetings from,
TJ

By the way this is not a good thread for your question as it is for as the servers give no new work. And you get plenty of work...

Thanks for the info, and sry for my spamming.

BOINC development version 6.12.18 is out. Testing 6.12.15 is not going to do the developers any good anymore.

16/03/2011 8:03:31 PM | Milkyway@home | Incomplete read of 1084.000000 < 5KB for de_separation_20_3s_fix_4_709807_1300265776_search_parameters - truncating
16/03/2011 8:05:04 PM | Milkyway@home | [error] File de_separation_10_3s_fix_5_710538_1300266237_search_parameters has wrong size: expected 636, got 0

Arrrgghhh!

Feeder, along with a bunch of other things, aren't running. can't get new tasks.


3/17/2011 5:52:19 PM Milkyway@home Scheduler request completed: got 0 new tasks
3/17/2011 5:52:19 PM Milkyway@home Message from server: Server error: feeder not running


http://milkyway.cs.rpi.edu/milkyway/server_status.php

/\ Feeder back online.

Validator is down again. 18k+

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Everything is down again...

ouch!

Aaaarrrggghhhhh!

Aaaaarrrrgggghhh!


Soon to be downloading half a days Collatz work.

---

Go away, I was asleep

Don't jump the gun too soon! Everything is up and running again after the outage. 5K worth of work to send out available.

---

I already left, be back when dnetc breaks or when I can be ersed to change over again

Problems again. No new work and ready work cannot be sent.
Six servers are red. We have to wait a while.

---

Greetings from,
TJ

I think that this outage might be intentional. The server has been sending out work units that cannot validate because either nobody can generate two results close enough to each other so that they can validate, or the validator fails and declares a validate error. Therefore, the flow of work units was probably stopped to fix what is wrong.

Servers Back... happy crunching!

regards!