Welcome to MilkyWay@home

Posts by mikey

21) Message boards : News : New Workunit Generation Pause (Message 68489)
Posted 7 Apr 2019 by Profilemikey
Post:
Hello,

I noticed that I don't have any tasks at this time, or work units. Is this related to the server migration? I am new to this, so I am not quite sure how it works.

~ Iuliana


No the transition to the new server is complete.
22) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68464)
Posted 1 Apr 2019 by Profilemikey
Post:
hi, I need atleast 8days worth of WU's stored, i need offline wu's for atleast 2days at a time, im doing 19s per WU_cheers


Unless you have a very slow gpu that won't happen here at MilkyWay, they don't want to tie up that many workunits on one machine at one time.
The key here is to return a wu so you can get another wu, recently that has been a minor problem but the Admin has been working very hard to get it back up and running like it did under the old Server side software version.
23) Message boards : Number crunching : No Stat's Export (Message 68388)
Posted 25 Mar 2019 by Profilemikey
Post:
Still not seeing stat exports as of 1906 UTC -0800 03/24/2019.

I know the server just switched to new hardware. Do you have to switch it back on?

Any ETA on when this will be fixed?

Best,

Prescott


They switched to a new version of the Server side Boinc Software and there are a TON of changes to them and if you change one thing it can affect a hundred other things you would never think are related, that means it could be a bit if they see it as a lower priority than some other things that also need fixing. Like computers being unable to connect, credits being awarded to EVERYONE with a valid result, which it wasn't as of yesterday, software not being auto downloaded like it should be meaning people can't crunch, etc ,etc. You haven't lost any credits so far, they just aren't being reported to the stats sites, what SHOULD happen is you, and everyone else, will get a big jump in credits on the stats sites one day and then you will know it's fixed. Jake will probably announce it too.
24) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68185)
Posted 24 Feb 2019 by Profilemikey
Post:
I really hope you will improve this situation.

I have concluded that if they are smart enough to map the galaxy, then they must be smart enough to know that by limiting the work units, they will lose the fastest machines to other projects (especially in view of all the server outages).

My guess is that they are getting enough work done with the slower machines to satisfy their needs. It may take time to analyze the results, for example, which can't be sped up further. So if that does not work for you, probably finding another project is the best solution. They all have their limits somewhere; there is not an infinite supply of work. We just need to move around to accommodate what they can supply at any given time.


I agree the new "Do You Feel Lucky? (GFN World Record))" workunits at PrimeGrid, suggested for high end gpu's only, takes about 2 days on a 1080Ti and you get almost 1 million credits for each one. And they will make as many as they have people willing to crunch them. For cpu workunits they have some that take over 100 days!!
25) Message boards : Number crunching : Stats dropping for several days. (Message 68101)
Posted 7 Feb 2019 by Profilemikey
Post:
I think I found the problem. Razer installed a mining program (to earn credits for Razer gear) on my machine. It's supposed to crunch with the GPU. I DISABLED it, but it still must've been affecting the GPU because my stats kept dropping until I UNINSTALLED it. My stats are climbing again!

https://www.dropbox.com/s/kh0g95ktyslp4zd/Screenshot%202019-02-06%2011.10.35.png


That makes sense. It may run alongside it just fine at a project that uses less of your gpu but MilkyWay uses alot of the gpu when crunching their units.
26) Message boards : Number crunching : GPU Issue (Message 68089)
Posted 1 Feb 2019 by Profilemikey
Post:
NVIDIA GeForce GT 635 Machine running WIN 7 PRO 64bit
Due to an ever increasing number of Driver crashes, I updated the driver to NVIDIA 417.71 Since that update, every GPU unit has failed in less than 3 seconds. Any thoughts?


Go back to the 3 series of drivers, alot of project don't support the new drivers for older hardware yet.


Thanks for the reply ... the driver that kept crashing was 353.?? I'll see if I can find something between 354 and 399


Version 398.11 was working for me.
27) Message boards : Number crunching : GPU Issue (Message 68082)
Posted 31 Jan 2019 by Profilemikey
Post:
NVIDIA GeForce GT 635 Machine running WIN 7 PRO 64bit
Due to an ever increasing number of Driver crashes, I updated the driver to NVIDIA 417.71 Since that update, every GPU unit has failed in less than 3 seconds. Any thoughts?


Go back to the 3 series of drivers, alot of project don't support the new drivers for older hardware yet.
28) Message boards : Number crunching : Server can't open database? (Message 68080)
Posted 31 Jan 2019 by Profilemikey
Post:
I see this has been happening for over 9 years. Can't anyone figure out and fix the root cause?
It happened again this morning.


I always assumed it was some process running, like a backup, cleanup, whatever that needed to close the database. But you are right every morning about the same time it goes off line.
29) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68068)
Posted 26 Jan 2019 by Profilemikey
Post:
By definition here at MW N-Body wu's are multi-core wu's.


No, there's also a single core N-Body application, see applications page.


Hmm I did not know that.... Thanks!!!
30) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68066)
Posted 25 Jan 2019 by Profilemikey
Post:
You do know you can turn each kind off individually in the settings...right?

Run only the selected applications MilkyWay@Home: yes
MilkyWay@Home N-Body Simulation: no


But that doesn't select between single-core and multi-core N-Body, does it?


Yes it does, if you unselect the "N-Body Simulation" units you won't get any more multi-core wu's, on the other hand if you unselect the "MilkyWay@Home" units then you won't get any more single core wu's.


No, it does not. With "MilkyWay@Home: yes", you will get single core MilkyWay@Home WUs (they are all single core), but not single core MilkyWay@Home N-Body Simulation WUs.


By definition here at MW N-Body wu's are multi-core wu's.
31) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68061)
Posted 24 Jan 2019 by Profilemikey
Post:
You do know you can turn each kind off individually in the settings...right?

Run only the selected applications MilkyWay@Home: yes
MilkyWay@Home N-Body Simulation: no


But that doesn't select between single-core and multi-core N-Body, does it?


Yes it does, if you unselect the "N-Body Simulation" units you won't get any more multi-core wu's, on the other hand if you unselect the "MilkyWay@Home" units then you won't get any more single core wu's.
32) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68057)
Posted 23 Jan 2019 by Profilemikey
Post:
But my point is if the NBody wu's don't work for everyone then going to it exclusively means lost crunchers.


They have already lost me, as I posted a couple of weeks ago. I won't go back until they have all multi-thread, or all single-thread. I don't care which.
But not all projects work for all crunchers. That is always the case.


You do know you can turn each kind off individually in the settings...right?

Run only the selected applications MilkyWay@Home: yes
MilkyWay@Home N-Body Simulation: no

Those are my settings here and as you can see I turned the n-body wu's off so I never get any. There are separate settings for the different kinds of gpu's too but they only run one wu at a time anyway.
33) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68055)
Posted 23 Jan 2019 by Profilemikey
Post:
I have 17 desktops that crunch for me, most have different cpu's in them so unless MW is going to be like PrimeGrid and add a whole bunch of venues I can't do that for my pc's. Setting the number of cpu's to 5 works fine for a 6 core pc but won't work for an 8 core, a 16 core or even a 24 core pc! I would very quickly run out of venues and then if I were to crunch Einstein on the gpu in a pc since they automatically reserve a cpu core just for the gpu to use no MW units would run at all. AND as I said before the MT wu's all crash for me, no idea why they just do.

You can always do it the hard way: use an app_config.xml file in the project folder. You can then set it to use only one core per work unit.

<app_config>
<app>
<name>milkyway_nbody</name>
<max_concurrent>8</max_concurrent>
</app>
<app_version>
<app_name>milkyway_nbody</app_name>
<plan_class>mt</plan_class>
<avg_ncpus>1</avg_ncpus>
</app_version>
</app_config>


Then, set the "<max_concurrent>" if you want to limit the number of work units running at once, and set "<avg_ncpus>" to use the number of cores per work unit.
Hopefully, that will prevent the crashing (I have never seen it though, and don't know what might be causing it).


Nope that didn't work for me, I think it's just a Win10 problem with my not made for Win10 hardware. The pc's crunches everything else except Climate Prediction but I've heard they have a higher than average error rate anyway so I have no clue. But my point is if the NBody wu's don't work for everyone then going to it exclusively means lost crunchers.

For me my gpu's work here just fine, it's just my cpu's that only work one way.
34) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68053)
Posted 22 Jan 2019 by Profilemikey
Post:
I would much rather run 6 workunits on 6 different cpu cores than 1 wu on 6 cpu cores at once.

Then you could just set the MW to run on a single core. That is what Jake was saying. With a multi-threaded application, you can set it to run on as many cores as you want, including one.

They would probably include an easy to set option in the preferences page in that case, such as LHC and Cosmology (usually called "Max # CPUs").


I have 17 desktops that crunch for me, most have different cpu's in them so unless MW is going to be like PrimeGrid and add a whole bunch of venues I can't do that for my pc's. Setting the number of cpu's to 5 works fine for a 6 core pc but won't work for an 8 core, a 16 core or even a 24 core pc! I would very quickly run out of venues and then if I were to crunch Einstein on the gpu in a pc since they automatically reserve a cpu core just for the gpu to use no MW units would run at all. AND as I said before the MT wu's all crash for me, no idea why they just do.

It's no my Project and I'm just crunching here so they can do what they want to do, but if they go to only MT wu's I won't be crunching cpu wu's here any more.
35) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68050)
Posted 21 Jan 2019 by Profilemikey
Post:
I am thinking, why do we even have a single threaded application? How would everyone feel about having only multithreaded, and if you want to run it single threaded wu you just choose to have 1 CPU used? Would that work?

Jake


If you do I think alot of people will leave MW, I personally hate running multi-core wu's as they never seem to work well with other projects when you guys for example run out of work. I would much rather run 6 workunits on 6 different cpu cores than 1 wu on 6 cpu cores at once. The other problem I have is the wu's don't work right on at least some peoples computers, I know you keep tweaking the program but it just doesn't work right on every pc, BUT the single core wu's work just fine.

Boinc also seems to have problems running multi-core wu's in general...I do run multi-core wu's on another project, running them as a single core wu takes 12 days or more, but since you can't set it for 3.5 cores for each wu I'm stuck with using 3 cores for each wu and then having 2 cores free, on an 8 cpu core machine, when I also run a wu on the gpu. Boinc itself won't fill the remaining cores with wu's because the setting is 3 cores per wu! That's a very inefficient way to run a pc!! I try to always leave one cpu core free for the gpu to use, leaving me 7 cpu cores to crunch cpu wu's, on that 8 core cpu machine. On a 6 cpu core machine it leaves me 5 cpu cores to crunch with again making it a problem. And yes I could set it for 7 or 5 cpu cores per wu but then we are back to the problem of your multi-threaded software not working for everyone.
36) Message boards : Number crunching : ati 5900 (Message 67927)
Posted 5 Dec 2018 by Profilemikey
Post:
I have a dual GPU ati 5900 . it generally runs one unit . but sometimes it runs 2 and takes a cpu to itself . I just caught something odd . when I want to watch any video I have to stop crunching [ rosetta and milky way ] it appears if I stop / snooze the work unit it goes out to 40 hours and the GPU is not crunching and is idling at 98 degrees , I just aborted several and it appears the downward trend started a couple of weeks ago


From the error message, Error creating command queue (-6): CL_OUT_OF_HOST_MEMORY
Error getting device and context (-6): CL_OUT_OF_HOST_MEMORY, it looks like the memory isn't being released after you watched the video. There is no way to reset a gpu in Windows without rebooting the machine so you may be stuck with only running 1 gpu and keeping the other one free for your video watching.
37) Message boards : Number crunching : Error while computing on many runs (Message 67920)
Posted 30 Nov 2018 by Profilemikey
Post:
Thanks, issue fixed with computer reboot.


That's good!
38) Message boards : Number crunching : Computation Error - frequently (Message 67919)
Posted 30 Nov 2018 by Profilemikey
Post:
Hi,

For some months, 99% of the tasks for this project are immediately ending with following error.

computation error (0.283 CPUs + 1 NVIDIA GPU)

Is this due to the graphics card?
The project has been removed and re-added to the Boinc Manager with no change.

Running on...

Intel(R) Core(tm)2 Duo CPU P7550 @ 2.26GHz
Graphics: NVIDIA GeForce 9400 256 MB
osx 10.11.6
Boinc Mgr v7.14.2

Thanks,
Nancy


Did you install the Nvidia drivers from Nvidia? The normal drivers coming with the OS aren't the right kind to crunch with. I looked at your pc and it doesn't say anything about the version of Nvidia driver you are using. And besides that a 256mg gpu is NOT powerful enough for her, I believe the minimum is 1gb of onboard memory for the gpu to work here.
39) Message boards : Number crunching : Error while computing on many runs (Message 67916)
Posted 29 Nov 2018 by Profilemikey
Post:
Over 300 runs today have ended with a message "error while computing." I am using MilkyWay@Home v1.46 (opencl_nvidia_101). Does anybody know what the problem is?


Nope because you have your computers hidden, we can't help you without being able to see what's going on.
40) Message boards : Number crunching : Why is this work unit running a long time? (Message 67911)
Posted 22 Nov 2018 by Profilemikey
Post:
I'm having similar problems:


Application
MilkyWay@Home N-Body Simulation 1.72 (mt)
Name de_nbody_10_24_2018_v172_20k__data_1_1540379102_33925
State Running
Received 11/11/2018 10:48:09
Report deadline 23/11/2018 10:48:07
Resources 6 CPUs
Estimated computation size 11,120 GFLOPs
CPU time 08:52:57
CPU time since checkpoint 03:04:39
Elapsed time 5d 02:56:59
Estimated time remaining 1d 06:09:50
Fraction done 80.300%
Virtual memory size 9.46 MB
Working set size 4.84 MB
Directory slots/2
Process ID 580
Executable milkyway_nbody_1.72_windows_x86_64__mt.exe

My pc is a Dell XPS Intel Core i7 3.4GHz 4 core 8 logical processors runint W10 Pro. Boinc and virtualisatoin software are up to date.


Ideas?

David Dewick


The n-body wu's do not work for everyone, that's why there are sooo many revisions all the time, in your settings you can choose not to run the n-body wu's which uses multiple cpu cores for one wu, and instead run one wu per cpu core.


Previous 20 · Next 20

©2019 Astroinformatics Group