Welcome to MilkyWay@home

Posts by Chaosquo

1) Message boards : Number crunching : Simultaneously CPU & GPU (Message 40429)
Posted 16 Jun 2010 by Chaosquo
Post:
I have set BOINC to only use 80% CPU time (for another project) and I get a slowdown of 10% for the GPU. I think it is a problem of priority/congestion ..
2) Message boards : Number crunching : NVIDIA running on diskless machine ? (Message 40269)
Posted 7 Jun 2010 by Chaosquo
Post:
afaik, MilkyWay does not yet support GT4xx GPUs. That should be the reason ..
3) Message boards : News : server is generating work again (Message 40260)
Posted 7 Jun 2010 by Chaosquo
Post:
I'm just curious, dont want to blame anyone: Why do the servers crash? Is it overload? Does a simple restart not help? Or is it always a different problem and you have to fix it before it works again?
4) Message boards : Number crunching : Boinc 6.10.56 - backup project (Message 40166)
Posted 3 Jun 2010 by Chaosquo
Post:
BOINC will periodically contact the project, so it will know when MW has new work available. But when MW has new work available, it will still finish all work that was requested from the backup project before returning to MW, thats why I said to not maintain too much work.
5) Message boards : Number crunching : Boinc 6.10.56 - backup project (Message 40155)
Posted 2 Jun 2010 by Chaosquo
Post:
I'm not sure if we mean the same thing: I meant to have an extra project as backup attached, but not running as long as MilkyWay has work. When there is no work for MilkyWay, BOINC will ask for work from the backup project.

You do this by going to the project you want to use as backup and go to "Preferences for this project". There you set the resource share to zero. That works for me.

Also note that you should not set "Maintain enough work for an additional" under "Computing preferences" too high, otherwise it will ask for too much work from the backup project. I have mine set to 0.05 days (1.2 hours), I can run 24 WUs from Milkyway in under an hour, so no point in maintaining more work (as MW does not give out more).
6) Message boards : Number crunching : Boinc 6.10.56 - backup project (Message 40134)
Posted 2 Jun 2010 by Chaosquo
Post:
This is a feature which was introduced after 6.0.18, so you should have to upgrade ..
7) Message boards : Number crunching : Boinc 6.10.56 - backup project (Message 40120)
Posted 1 Jun 2010 by Chaosquo
Post:

This change requires a server side update ... I don't think EaH has made the changes yet. Based on the report above I can almost assure you that they have not ... at the moment there are only a few projects using the newest and capable server software that will allow this ... SaH, Collatz are two I know ... DNETC just indicated that they have updated the server software but I have not tried to see if this is possible there ...

One of the problems with BOINC is that when projects customize the software for their own needs and UCB throws in something like this, well, it causes problems because they do not have sufficient isolation in some of the parts ... so ...

As far as I am concerned, DNETC works just fine as backup project (as long as the server is up). BOINC switches to DNETC when there is no work on MW and switches back when there is work.
8) Message boards : Number crunching : Boinc 6.10.56 - backup project (Message 40011)
Posted 28 May 2010 by Chaosquo
Post:
I set it to 0 on the DNETC website and it also shows at 0 in the BOINC Manager.
9) Message boards : Number crunching : Boinc 6.10.56 - backup project (Message 40009)
Posted 28 May 2010 by Chaosquo
Post:
I read in the release notes of Boinc 6.10.56 that you can now setup a backup project by setting its resource share to 0. I did this with DNETC, but it as soon as I resume it, BOINC suspends MW and starts DNETC. Could it be that I still have a unfinished WU in DNETC, which is causing this? Anyone got this feature to work?

edit: I read in here: http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1681#38673 that it seems to be a problem of DNETC being too greedy?
so could you suggest me another project as backup for a 5850 besides Collatz (I just dont see the point of testing big numbers if they work with the Conjecture .. but thats another discussion)
10) Message boards : Number crunching : v0.23 performance drop? (Message 39825)
Posted 19 May 2010 by Chaosquo
Post:
Finally somone with the same problem ... Thank you for your advice.
Sadly, leaving a whole CPU core free for assiting the GPU is not an option for me, but as I said, leaving WMP running in the background running on repeat has almost solved the problem for me (just 5 secs slower). I guess its because WMP stops Climate Prediciton from using all the CPU time.
11) Message boards : Number crunching : v0.23 performance drop? (Message 39709)
Posted 14 May 2010 by Chaosquo
Post:
But I have the complete opposite effect: If I dont use my PC at all, but crunch on the CPU, the work gets done the slowest. If it is in light use, but also crunching on the CPU, works gets done faster. And if I stop the crunching of the other BOINC task on my CPU, works gets done fastest.

btw, I allowed crunching on the GPU while the computer is in use.
12) Message boards : Number crunching : Big issue : Milkiway doesn't work on Mac OS X. (Message 39701)
Posted 14 May 2010 by Chaosquo
Post:
I just noticed I have the same problem, but on Win 7 x64. I run MilkyWay on a HD 5850 and each time I suspend and resume a WU, the WU gets restarted. Is this behaviour intentional? Its no big problem, I only lose a minute or two, just curious.
13) Message boards : Number crunching : v0.23 performance drop? (Message 39700)
Posted 14 May 2010 by Chaosquo
Post:
I did some testing:
I booted my PC and started BOINC immediately and got a WU completion time of 130 sec. After half an hour, I started used Windows Media Player to play some music and the completion time immediately dropped down to 115 sec.

My system:
Win7 Prof x64, i5-750, HD5850

What could be causing this strange behaviour?
14) Message boards : Number crunching : v0.23 performance drop? (Message 39689)
Posted 13 May 2010 by Chaosquo
Post:
I have the same system and get the same problem. I dont allow MilkyWay to do work on the CPU. If I dont have a BOINC task running on the CPU, I get a WU done in 110 sec. If I let the CPU do work (in my case Climate prediction), it goes up to 130 secs.
What is also strange that sometimes I get down to 115 secs, but only when the PC is also in use (listening to music, browsing Internet etc).

Any idea what is causing this?




©2022 Astroinformatics Group