1)
Message boards :
Number crunching :
UV reionization tasks fail
(Message 1396)
Posted 21 Aug 2016 by Bryan Post:
Thank you for the update. On a new app it is appreciated. My Linux machines are having no problems and most Win7 machines are also working fine. I do have 1 machine that errors ever WU immediately. That machine is absolutely identical (hw and sw) to 2 other machines that aren't having any problems. |
2)
Message boards :
Number crunching :
Too much WUs
(Message 811)
Posted 25 Nov 2015 by Bryan Post:
Then don't ask for one. The project was giving you what you are asking for and others can use. It isn't the responsibility of the project to "protect you from yourself". If I want a full cache then I should be able to get one. If I don't want it full then I drop the size of my request. |
3)
Message boards :
Number crunching :
ULX credits
(Message 807)
Posted 25 Nov 2015 by Bryan Post: This will be corrected manualy by krzyszp. That will work :) |
4)
Message boards :
Number crunching :
ULX credits
(Message 798)
Posted 24 Nov 2015 by Bryan Post: I see the new ULX 48 WUs take 3.4 times longer to process and pay the same 333 credits? If that is intended then how about loading up some BHspin or V4 WU. A BHspin takes roughly the same computational time and pays 4 times the credits. |
5)
Message boards :
Number crunching :
Too much WUs
(Message 796)
Posted 24 Nov 2015 by Bryan Post: Meanwhile i let one of my hosts get new work and controlled how much it got. No, 7 WU / thread is no where near enough. On my machines 7 WU will last 10.5 hours on a single thread. If your processor can't handle the load then control the number of WU you get with the "additional work buffer" setting in the BOINC manager. You said you have it set for 10 days so you aren't even getting the work you are asking for. |
6)
Message boards :
Number crunching :
Too much WUs
(Message 794)
Posted 24 Nov 2015 by Bryan Post: All my machines are now running in High Priority Mode because the cached WU are showing 30 days required to complete a single WU. You need to reset the estimated time. For example, I have 1 machine running Linux that has 12 WU in progress and all were started at the same time. 11 WU say they will finish in 40 minutes and the 12th WU says 30 days and 3 hours required to finish. All should be finish in 1 1/2 hours total. The 11 WU in cache are estimating it will require 339 days to complete them. While the machines are in this state I can not run other projects. |
7)
Message boards :
News :
New applicaion
(Message 484)
Posted 20 Aug 2015 by Bryan Post:
Well in that case you should be at 555 since this is a new app: Change is in the air when you see 5:55. Like a fast moving current or a gentle breeze, there is momentum to move in a new direction BTW, at 333 the project is paying less than before. Not complaining, just pointing it out. |
8)
Message boards :
News :
New applicaion
(Message 461)
Posted 15 Aug 2015 by Bryan Post: Have the new tasks a longer runtime? Yes, about 2x. |
9)
Message boards :
Number crunching :
Server is dry - or what?
(Message 375)
Posted 19 Jun 2015 by Bryan Post: Now that we have work (thank you), can you turn the validator back on? :) |
10)
Message boards :
Number crunching :
Server is dry - or what?
(Message 374)
Posted 19 Jun 2015 by Bryan Post: Great! The machines need something to chew on :) |
11)
Message boards :
Number crunching :
Server is dry - or what?
(Message 367)
Posted 18 Jun 2015 by Bryan Post: You might need to kick him twice :) There is a 3 day team challenge starting in 11 hours and I expect the server is going to see a big increase in demand. |
12)
Message boards :
Number crunching :
Old Universe@Home Test
(Message 347)
Posted 3 Jun 2015 by Bryan Post: It looks like BStats has the right info now... my credits returned to where they were supposed to be. Thanks for the help ... although I wasn't going to worry about it anyway :) |