Welcome to MilkyWay@home

Updates not happening automatically

Message boards : Number crunching : Updates not happening automatically
Message board moderation

To post messages, you must log in.

AuthorMessage
tmath250

Send message
Joined: 15 Jan 12
Posts: 11
Credit: 89,558,167
RAC: 0
Message 53406 - Posted: 24 Feb 2012, 14:27:50 UTC

Forgive if this is in another thread (I did search!), but After running one update, there is no more updating! If I press teh Update button, it does, timer starts to update 60S later, but once the 2nd update occurs, no more automatic update!
I have tried shutting down, re-booting to no avail.
Any help GREATLY appreciated! I can't stay here and keep pressing update to get more work!

Was using BOINC manager 6.12.34, now 7.0.18 and same problem.

Asus Rampage IV Extreme
32 GB RAM
(2) MSI Radeon HD 7970
Catalyst 12.3
ID: 53406 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Zydor
Avatar

Send message
Joined: 24 Feb 09
Posts: 620
Credit: 100,587,625
RAC: 0
Message 53408 - Posted: 24 Feb 2012, 14:59:13 UTC
Last modified: 24 Feb 2012, 15:03:40 UTC

They made changes to updating/refills for 7.X.X, and has resulted in different behaviour than (generally) in 6.X.X.

Basicly, with 7.X.X perceptions need to shift a little. Refills are more strictly controlled by the software, and less scope for manual downloads accumulating large caches. MW has its own limiter of course - 40 per GPU - but that still is caught under the whole overarching refill mechanism in 7.X.X

It will tend to run down cache (not always, just beaware it can leave it somewhat late!) until the last minute, and then refill. So, at the least sit back and let it do it thing, dont apply expectations of 6.X.X behaviour, it will not happen. The other change behaviourily, is - by in large - it now tends to download one or two WU at a time, not a big wack of them at once (MWs are short so you get lots of those in one go). Again, dont try to fight it (you'll lose rofl), let it do its thing. For example a dry machine on startup left overnight is rewarded with a full cache when you get up :)

There are still problems with aspects of the work fetch, but take on board the two behavioural changes above, as they are the most misunderstood, and nothing is wrong as such, the software is working "as designed" - just that its designed differently in V7.X.X

Regards
Zy
ID: 53408 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
tmath250

Send message
Joined: 15 Jan 12
Posts: 11
Credit: 89,558,167
RAC: 0
Message 53412 - Posted: 25 Feb 2012, 1:21:43 UTC

Funny, I've been praying for patience lately! I guess I should accept this as an answer to my prayers!
:)
ID: 53412 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Zydor
Avatar

Send message
Joined: 24 Feb 09
Posts: 620
Credit: 100,587,625
RAC: 0
Message 53414 - Posted: 25 Feb 2012, 2:07:13 UTC - in response to Message 53412.  

Funny, I've been praying for patience lately! I guess I should accept this as an answer to my prayers!
:)

Thats doomed the pair of us ..... Murphy will descend like bees to a honey pot :)

Regards
Zy
ID: 53414 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[boinc.at] Nowi

Send message
Joined: 22 Mar 09
Posts: 99
Credit: 503,422,495
RAC: 0
Message 53416 - Posted: 25 Feb 2012, 9:36:44 UTC
Last modified: 25 Feb 2012, 9:37:01 UTC

I´m using 7.0.18 with a pretty full cache for both, GPU (M@W) and CPU (several projects), by using this network preferences:

Minimum work buffer: 1.00 days
Max. additional work buffer: 0.01 days.

It runs pretty smooth. Try this... :)

Cheers

Nowi
ID: 53416 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Beyond
Avatar

Send message
Joined: 15 Jul 08
Posts: 383
Credit: 729,293,740
RAC: 0
Message 53421 - Posted: 25 Feb 2012, 15:05:11 UTC - in response to Message 53408.  

They made changes to updating/refills for 7.X.X, and has resulted in different behaviour than (generally) in 6.X.X.

Basicly, with 7.X.X perceptions need to shift a little. Refills are more strictly controlled by the software, and less scope for manual downloads accumulating large caches. MW has its own limiter of course - 40 per GPU - but that still is caught under the whole overarching refill mechanism in 7.X.X

It will tend to run down cache (not always, just beaware it can leave it somewhat late!) until the last minute, and then refill. So, at the least sit back and let it do it thing, dont apply expectations of 6.X.X behaviour, it will not happen. The other change behaviourily, is - by in large - it now tends to download one or two WU at a time, not a big wack of them at once (MWs are short so you get lots of those in one go). Again, dont try to fight it (you'll lose rofl), let it do its thing. For example a dry machine on startup left overnight is rewarded with a full cache when you get up :)

There are still problems with aspects of the work fetch, but take on board the two behavioural changes above, as they are the most misunderstood, and nothing is wrong as such, the software is working "as designed" - just that its designed differently in V7.X.X

I'm usually an early adopter of new BOINC versions but so far I've heard many negatives regarding BOINC 7.x. Are there any positives? 6.12.41 & 6.12.43 seem to run with no real issues.
ID: 53421 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Zydor
Avatar

Send message
Joined: 24 Feb 09
Posts: 620
Credit: 100,587,625
RAC: 0
Message 53422 - Posted: 25 Feb 2012, 15:25:11 UTC

Its a big change ..... brave new world of OpenCL for all, with added flavour of VM's .... takes time I guess, it is still Alpha.

Problem is the number of Projects needing that OpenCL flavour inside BOINC is growing, so the pressure is on ..... *turn the sound up & pass the popcorn*, it aint over yet :)

Regards
Zy
ID: 53422 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Beyond
Avatar

Send message
Joined: 15 Jul 08
Posts: 383
Credit: 729,293,740
RAC: 0
Message 53425 - Posted: 25 Feb 2012, 21:56:30 UTC - in response to Message 53422.  

For years we've been asking for more control over the number of WUs that can be downloaded by particular projects. Instead, 7.x gives us less control than ever. Why take control away from the users and projects? What's the real agenda driving these changes?
ID: 53425 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
tmath250

Send message
Joined: 15 Jan 12
Posts: 11
Credit: 89,558,167
RAC: 0
Message 53431 - Posted: 26 Feb 2012, 2:08:02 UTC

I´m using 7.0.18 with a pretty full cache for both, GPU (M@W) and CPU (several projects), by using this network preferences:

Minimum work buffer: 1.00 days
Max. additional work buffer: 0.01 days.

It runs pretty smooth. Try this... :)

Cheers

Nowi


I tried your suggestion. Since cache was running low, I hit "Update". Here is what the event log said.

2/25/2012 8:05:33 PM | Milkyway@Home | update requested by user
2/25/2012 8:05:37 PM | Milkyway@Home | Sending scheduler request: Requested by user.
2/25/2012 8:05:37 PM | Milkyway@Home | Reporting 20 completed tasks, not requesting new tasks
2/25/2012 8:05:38 PM | Milkyway@Home | Scheduler request completed
ID: 53431 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Zydor
Avatar

Send message
Joined: 24 Feb 09
Posts: 620
Credit: 100,587,625
RAC: 0
Message 53432 - Posted: 26 Feb 2012, 2:38:38 UTC - in response to Message 53425.  
Last modified: 26 Feb 2012, 2:39:47 UTC

For years we've been asking for more control over the number of WUs that can be downloaded by particular projects. Instead, 7.x gives us less control than ever. Why take control away from the users and projects? What's the real agenda driving these changes?


My guess - and its only that, I have no factual basis for saying it, just a gut instinct.... I suspect its all about reducing cache levels, as many held caches are more than crazy - compounded by continual runaway machines dumping out large caches.

The problem is at the server end, the database sizes rise exponentially when large caches are held, with one of two results - either it slows down horribly, or gets worse as it cant fit the database(s) in memory. It was the latter that was the issue here. Tracking each issued WU takes a lot of time and space, and if too many out there, it can bring down a server that has less clout than most.

Lots of easy knee jerk resonses to that of course, but life is different if sitting at the server end as an admin. Lots of other solutions around to all that, but I have a feeling its a rose tinted view from this end, compared to when at the server end in the middle of the mire :)

Regards
Zy
ID: 53432 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
tmath250

Send message
Joined: 15 Jan 12
Posts: 11
Credit: 89,558,167
RAC: 0
Message 53434 - Posted: 26 Feb 2012, 2:52:30 UTC

I´m using 7.0.18 with a pretty full cache for both, GPU (M@W) and CPU (several projects), by using this network preferences:

Minimum work buffer: 1.00 days
Max. additional work buffer: 0.01 days.

It runs pretty smooth. Try this... :)

Cheers

Nowi




Thanks! I had screwed up those exact settings (Basically reversed them). Works MUCHO better now! Thanks!
:)
ID: 53434 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Updates not happening automatically

©2024 Astroinformatics Group