Posts by mikey
|
1)
Message boards :
News :
Micromanaging CPU vs GPU Workunit Limits
(Message 68185)
Posted 25 days ago by  mikey
Post: I really hope you will improve this situation. 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!! |
|
2)
Message boards :
Number crunching :
Stats dropping for several days.
(Message 68101)
Posted 7 Feb 2019 by mikey
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! 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. |
|
3)
Message boards :
Number crunching :
GPU Issue
(Message 68089)
Posted 1 Feb 2019 by mikey
Post: NVIDIA GeForce GT 635 Machine running WIN 7 PRO 64bit Version 398.11 was working for me. |
|
4)
Message boards :
Number crunching :
GPU Issue
(Message 68082)
Posted 31 Jan 2019 by mikey
Post: NVIDIA GeForce GT 635 Machine running WIN 7 PRO 64bit Go back to the 3 series of drivers, alot of project don't support the new drivers for older hardware yet. |
|
5)
Message boards :
Number crunching :
Server can't open database?
(Message 68080)
Posted 31 Jan 2019 by mikey
Post: I see this has been happening for over 9 years. Can't anyone figure out and fix the root cause? 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. |
|
6)
Message boards :
News :
Micromanaging CPU vs GPU Workunit Limits
(Message 68068)
Posted 26 Jan 2019 by mikey
Post: By definition here at MW N-Body wu's are multi-core wu's. Hmm I did not know that.... Thanks!!! |
|
7)
Message boards :
News :
Micromanaging CPU vs GPU Workunit Limits
(Message 68066)
Posted 25 Jan 2019 by mikey
Post: You do know you can turn each kind off individually in the settings...right? By definition here at MW N-Body wu's are multi-core wu's. |
|
8)
Message boards :
News :
Micromanaging CPU vs GPU Workunit Limits
(Message 68061)
Posted 24 Jan 2019 by mikey
Post: You do know you can turn each kind off individually in the settings...right? 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. |
|
9)
Message boards :
News :
Micromanaging CPU vs GPU Workunit Limits
(Message 68057)
Posted 23 Jan 2019 by mikey
Post: But my point is if the NBody wu's don't work for everyone then going to it exclusively means lost crunchers. 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. |
|
10)
Message boards :
News :
Micromanaging CPU vs GPU Workunit Limits
(Message 68055)
Posted 23 Jan 2019 by mikey
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. 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. |
|
11)
Message boards :
News :
Micromanaging CPU vs GPU Workunit Limits
(Message 68053)
Posted 22 Jan 2019 by mikey
Post: I would much rather run 6 workunits on 6 different cpu cores than 1 wu on 6 cpu cores at once. 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. |
|
12)
Message boards :
News :
Micromanaging CPU vs GPU Workunit Limits
(Message 68050)
Posted 21 Jan 2019 by mikey
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? 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. |
|
13)
Message boards :
Number crunching :
ati 5900
(Message 67927)
Posted 5 Dec 2018 by mikey
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. |
|
14)
Message boards :
Number crunching :
Error while computing on many runs
(Message 67920)
Posted 30 Nov 2018 by mikey
Post: Thanks, issue fixed with computer reboot. That's good! |
|
15)
Message boards :
Number crunching :
Computation Error - frequently
(Message 67919)
Posted 30 Nov 2018 by mikey
Post: Hi, 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. |
|
16)
Message boards :
Number crunching :
Error while computing on many runs
(Message 67916)
Posted 29 Nov 2018 by mikey
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. |
|
17)
Message boards :
Number crunching :
Why is this work unit running a long time?
(Message 67911)
Posted 22 Nov 2018 by mikey
Post: I'm having similar problems: 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. |
|
18)
Message boards :
Number crunching :
Query on project consistency.
(Message 67909)
Posted 21 Nov 2018 by mikey
Post: I am very new to helping with number crunching and recently had an issue of completed tasks that would not report, I then received a message that the project URL needed to be updated which stated I should reattach the project. When I did this it deleted 47 completed tasks. You are using BAM to attach to the project...right? They are the ones that messed up!! The url was NOT wrong, it was changed and by deleting the project as THEY told you too that's why your units were lost. The old url DOES still work it's just not as fast, so you could have stayed with it until the units were returned and then switched. BAM is the problem THEY had the wrong url not you!! BTW you are far from the only person to have this happen too, it's the inaccurate error message they sent out. With a crunching pool you are limited to the projects you can crunch for and still get paid for your work, PrimeGrid just took their name off the list and other projects are considering it. You CAN still crunch for them, but you won't make any money while doing it. Gridcoin has a 'whitelist' that tells you which projects they will pay for. |
|
19)
Message boards :
Number crunching :
My unsent units are climbing gain
(Message 67904)
Posted 18 Nov 2018 by mikey
Post: I only have one host running MW, but have no issues with unsent WU's in my Pending list. I just checked my own list and it's down to under 20 but not by very much!! The 'problem' is MW does it differently than other projects, the wingman does NOT get your wu to validate until AFTER you return it!! So if the database hiccups and doesn't recognize that you have units waiting for a wingman it will send people a previously unsent wu to crunch instead. |
|
20)
Message boards :
Number crunching :
My unsent units are climbing gain
(Message 67900)
Posted 17 Nov 2018 by mikey
Post: Well I uploaded a bunch last night, but I am not accepting new work, so I don't know about that. Thank you for that but you don't seem to have as much of a problem as I do, maybe I have too many pc's on here is my problem. |
Next 20
©2019 Astroinformatics Group