Welcome to MilkyWay@home

Posts by Jesse Viviano

1) Message boards : Number crunching : Milkyway@home N-Body Simulation v1.82 (mt) windows_x86_64 stuck (Message 76381)
Posted 13 Sep 2023 by Jesse Viviano
Post:
I had one that was stuck. I eventually shut BOINC down to perform a OS update and GPU driver update. After rebooting, the stuck task suddenly rushed towards completion and quickly finished. Maybe all that you needed to do is to quit BOINC with the option to shut down all tasks with it, and then restart BOINC.
2) Message boards : Number crunching : Validation Pending too many tasks (Message 74471)
Posted 17 Oct 2022 by Jesse Viviano
Post:
I am wondering if something is wrong with either the transitioner or the validator. When sufficient numbers of successful task for a work unit are turned in, it is normally the job of the transitioner to send the work unit to the validator's queue. The validator can then declare the tasks as valid, invalid, or having an inconclusive validation where another task must be generated for the work unit so that the validator can try again with more results. Generally, inconclusive for most projects means that one of the tasks appears to be bad, so another task must be made to find and disqualify the bad result. This project uses that for either that or when it decides that it needs more tasks before validation can be performed. I have noticed that when the transitioner malfunctions in some projects, I have to wait for my result to hit its deadline. At the time that the deadline passes, something notices that enough tasks to attempt validation of the work unit have been returned, so the work unit is sent to the validator instead of having another task generated to replace a late task.

I have noticed that the only tasks in my queue that are validating are the ones that have 3 or more tasks in the work unit.

I currently have taken my machine off of BOINC duty, but that is because my apartment's air conditioner has failed and has nothing to do with this project's validation problem.
3) Message boards : Number crunching : Validation Pending too many tasks (Message 74387)
Posted 8 Oct 2022 by Jesse Viviano
Post:
I have the same problem, but I do not have the same problem with invalid or erroneous tasks that the original poster has. I have no invalid or erroneous tasks listed for my computer.
4) Message boards : Number crunching : Work units awaiting validation from January 24, 2019 (Message 68095)
Posted 3 Feb 2019 by Jesse Viviano
Post:
Please see https://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1713880117 and https://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1713879958. Can someone figure out why these old work units whose results were turned in on January 24, 2019 are not being validated yet?
5) Message boards : Number crunching : Errors (Message 66631)
Posted 17 Sep 2017 by Jesse Viviano
Post:
I made a bad post because I failed to read the date on the thread I linked to. Please ignore.
6) Message boards : Number crunching : Nvidia GPU compute client only doing 1/5 of the required work (Message 66374)
Posted 5 May 2017 by Jesse Viviano
Post:
Either a new driver or the new application version fixed the bug.
7) Message boards : Application Code Discussion : AVG detecting/blocking Milkyway App due to malware/virus? (Message 66370)
Posted 4 May 2017 by Jesse Viviano
Post:
Submit the false positive at https://secure.avg.com/submit-sample.
8) Message boards : Number crunching : Nvidia GPU compute client only doing 1/5 of the required work (Message 66285)
Posted 9 Apr 2017 by Jesse Viviano
Post:
I just filed a bug report with Nvidia over this issue.
9) Message boards : Number crunching : Nvidia GPU compute client only doing 1/5 of the required work (Message 66269)
Posted 3 Apr 2017 by Jesse Viviano
Post:
There is no sign that Windows 10 reinstalled any driver. Since other projects' GPU work still is being turned in and successfully validating, I would think that the problem is either a bug exists in the driver, or a new optimization in the driver exposed a previously undetected bug in the GPGPU software client (the latter has happened with Folding@home).
10) Message boards : Number crunching : Nvidia GPU compute client only doing 1/5 of the required work (Message 66267)
Posted 3 Apr 2017 by Jesse Viviano
Post:
The problem is back. I have had to disable GPU work for MilkyWay@home for now.
11) Message boards : Number crunching : Nvidia GPU compute client only doing 1/5 of the required work (Message 66266)
Posted 3 Apr 2017 by Jesse Viviano
Post:
I reinstalled my video driver using a clean install, and that seems to have fixed the problem.
12) Message boards : Number crunching : Nvidia GPU compute client only doing 1/5 of the required work (Message 66262)
Posted 2 Apr 2017 by Jesse Viviano
Post:
I also noticed that I am using the SSE4.1 path when my CPU, a Xeon E5-2690 v3, is capable of using AVX. In the work units where the GPU client failed, those who did the cleanup work after my computer messed up were using an AVX path. Could something be wrong with the SSE4.1 code path?
13) Message boards : Number crunching : Nvidia GPU compute client only doing 1/5 of the required work (Message 66261)
Posted 2 Apr 2017 by Jesse Viviano
Post:
I recently had to shut off GPU work for this project in my preferences because the Nvidia GPU client was only doing the final work unit in the now-standard 5 work unit bundle, causing my work to be declared as validate errors. The client was working fine until April 1 (No, this is no April fools joke.) My GPU is still generating valid work for other projects. Is anyone else having a similar problem?
14) Message boards : Number crunching : WU restart every 20% (Message 65988)
Posted 7 Dec 2016 by Jesse Viviano
Post:
There is a bug in how percentages are calculated by the MilkyWay@home application. As for why your work units are slower, the newer work units bundle 5 of the older work units into one bigger work unit to reduce BOINC server load because double-precision capable GPUs run these tasks much faster than CPUs, causing GPU crunchers to overwhelm the BOINC server.
15) Message boards : News : Scheduled Maintenance Concluded (Message 65812)
Posted 14 Nov 2016 by Jesse Viviano
Post:
Actually, 32-bit applications waste plenty of time in the memory system that 64-bit applications can often avoid because AMD doubled the number of registers in the register files from 8 to 16 while creating AMD64. Some programs will be able to fit all of their speed-critical data into the registers like AQUA@home used to do when it was active with its 64-bit application while the 32-bit version kept having to shuffle data into and out of the memory causing it to be significantly slower. However, the speedup a GPU provides overcomes the problems that 32-bit x86 provides like memory system overhead and conversion of 32-bit calls to OpenCL to 64-bit calls to OpenCL, but every little bit of speed helps.
16) Message boards : News : Scheduled Maintenance Concluded (Message 65717)
Posted 12 Nov 2016 by Jesse Viviano
Post:
I think that there is no need to suspend the project while these problems persist. Configure your MilkyWay@home preferences to only accept CPU work and not GPU work.
17) Message boards : News : Scheduled Maintenance Concluded (Message 65703)
Posted 12 Nov 2016 by Jesse Viviano
Post:
Thanks. Another speculative possibility that I should have thought of is that the Windows Nvidia GPU client might be running the work units in the CPU instead of the GPU because it is using as much CPU as a single core CPU client.
18) Message boards : News : Scheduled Maintenance Concluded (Message 65697)
Posted 12 Nov 2016 by Jesse Viviano
Post:
I am getting a 0% load on my GPU as measured by TechPowerUp GPU-Z that can be downloaded from https://www.techpowerup.com/downloads/. I think that your application is wasting a significant amount of time in between the time each work unit is being processed.
19) Message boards : News : Scheduled Maintenance Concluded (Message 65692)
Posted 12 Nov 2016 by Jesse Viviano
Post:
Work units that are generated with the old version of MilkyWay@home that need additional processing are causing errors. See https://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1386764939 for an example. It was generated for the old version of MilkyWay@home, and it needs additional runs for validation. Either the new version needs to be able to deal with results from old work units, or the new version should be listed as a new application so that old work units continue to be processed with the old version.
20) Message boards : Number crunching : Massive server issues and Wu validation delays (Message 65544)
Posted 28 Oct 2016 by Jesse Viviano
Post:
MilkyWay@home has some tasks that cannot be done on GPUs: the N-Body Simulation tasks. I think that this project should feed those first to CPUs and only send other tasks (both of which can be processed on GPUs) to CPUs if the scheduler runs out of N-Body Simulation tasks.


Next 20

©2024 Astroinformatics Group