Posts by ProDigit

1) (Message 6715)
Posted 21 May 2020 by ProDigit
Post:
I currently have about 500 WUs pending to upload.
I would recommend to configure not to accept new tasks, or lower the project's priority settings, so your PC will do other work (like Milkyway is still working).
2) (Message 6714)
Posted 21 May 2020 by ProDigit
Post:
Is there any application or newer version other than Period Search Application v102.12 (arm_android_pie) for Android devices? This thing runs too sloooooow. The last WU spent 46hrs on my Android TV-box. The TV-box run SCC from WCG before, very fast, 4 to 5 WUs per day. I check RAM and ROM to see if it was out of space, it was not. It was just too damn slow. Why? It there an alternative?

Most WUs run over 10 hours on ARM processors (2Ghz or below).
3) (Message 6705)
Posted 21 May 2020 by ProDigit
Post:
No, I compare it to most other projects.
Asteroids and mindmodelling are 2 projects that give the lowest PPD.
Most other have higher PPD.
PrimeGrid, GpuGrid, Yoyo are a bit higher.
The Collatz is without a doubt, giving too high PPD.

GPUs can't perform all the smart operations that CPUs can.
Some projects have more limited multitasking possibilities than others. Some have none at all which is why not all projects have GPU versions.
Comparison of GPU project performance is thus futile - by the way you failed to mention milkyway and Primegrid Genefer GPU WUs.

It is reassuring that Asteroids gives the same credit per WU whatever the process.

The smaller the CPU involvement, the greater the amount transferred to the GPU. This should be considered a measure of efficiency - not the opposite.

In case you didn't notice, all projects I mentioned above are GPU projects!
They all run NVidia GPUs.
When I see Asteroids on my NVidia GPU running at 198W, I assume I'll get pretty close to the same points as all other projects that can make use of the hardware in a similar manner.
If we get to compare, Asteroids uses the GPU way more intensely, than Einstein, Milkyway (which I didn't add, because I run plenty of GPU projects), and Moo! Wrapper. All these projects use about 1/3rd the power of my GPU (75W/104W Milkyway/Moo! -180W for einstein), yet they give more than 3x the credit Asteroids gives!

I'm telling you, this credit system stinks!

It's not even close to measured out fairly compared to all other projects that use the cobblestone measuring unit!

I would seriously recommend Astroids to stick to the standard laid out here:
https://boinc.berkeley.edu/wiki/Computation_credit

Likewise, I'm complaining with the Collatz for using Q/HPP (8-16bit) computation, but assigning 64bit DPP PPD for it!
This system is totally unfair as well!


I think Asteroids need to update their PPD credit system for GPUs,
Especially when they regularly shut down, and don't accept WUs from people, allowing processed WUs to expire without the user being able to upload them!

Srsly dude!
Asteroids is in the wrong here!
4) (Message 6702)
Posted 20 May 2020 by ProDigit
Post:
I'm not sure which is worse: the project periodically running out of work units and going a few days with nothing, or the project periodically running out of disk space for a few days in which WUs cannot be uploaded.....


Actually, I guess I prefer the latter. At least my machines remain gainfully employed, even if they can't upload. It'll catch up eventually....

I prefer the former.
I have plenty of projects I'm supporting, so if one goes down, i can do the second.
What's the worst, is when a project can't accept new WUs, and those WUs pass the deadline!
No PPD for them!

I'm having close to 200 WUs pending for upload....
5) (Message 6701)
Posted 20 May 2020 by ProDigit
Post:
No, I compare it to most other projects.
Asteroids and mindmodelling are 2 projects that give the lowest PPD.
Most other have higher PPD.
PrimeGrid, GpuGrid, Yoyo are a bit higher.
The Collatz is without a doubt, giving too high PPD.
6) (Message 6686)
Posted 19 May 2020 by ProDigit
Post:
Been trying to upload for an entire 2 days now!
Better get another (10TB) HDD, because it'll be full again soon!
7) (Message 6680)
Posted 18 May 2020 by ProDigit
Post:
CPU time for Astroids on Nvidia GPUs, record way too little CPU time.
I think the points are linked. Compared to most GPU projects, we're getting a good 8 to 10x lower points than we should receive.

Can points be revised pls?
8) (Message 6648)
Posted 4 May 2020 by ProDigit
Post:
Glad I'm not alone, and have an answer now.
Hope the problem gets fixed before the WUs expire!

Nothing around here happens in a hurry. My guess is they don't look at the server more than once a week, if that, and never on a weekend. Yes, I'm guessing because the admins of this project don't bother to communicate with the community at all. The history has been if something happens between Friday PM and Monday AM nothing gets done until Monday around noon if we are lucky.


Must be too busy drinking beer. If Asteroids is in Europe, they won't work in the weekends!
9) (Message 6647)
Posted 4 May 2020 by ProDigit
Post:
Re Collatz points on different GPU:
Turing class cards are way faster than Pascal on Collatz due to half precision capabilities:
https://en.wikipedia.org/wiki/List_of_Nvidia_graphics_processing_units#GeForce_16_series

Yeah, I think they do hpp and count it as FPP or DPP or something...
10) (Message 6632)
Posted 30 Apr 2020 by ProDigit
Post:

I came here because I've been running a few batches of asteroids on 2080Tis and feel like I get WAY too little credit for it.
Granted, about 80Wus still need to be validated, but I feel we're not getting an equivalent PPD score on asteroids, vs on most other projects.


Think 'credit new' for the credits here, they use the Seti idea of granting credits while other Projects like Collatz have their own idea of how many credits you should get for each workunit. If you just care about credits, most people don't BTW, then for gpu's crunch for Collatz and for cpu's crunch for http://nci.goofyxgridathome.net/ when they have workunits. I believe those are the two highest paying Projects at the moment.

I'm not looking for max amount of points.
But asteroids is by far the lowest PPD per hour of any GPU project!
On average I get the same PPD as my CPU crunching (in the likes of 200k PPD, vs 1M to 2M PPD on other projects. (The collatz gets me 80M PPD, and I'm not saying we should follow that, but at least be more equal to the other projects?).
11) (Message 6620)
Posted 28 Apr 2020 by ProDigit
Post:
I stand corrected, some of the new WUs only utilize less than 5% of CPU.
12) (Message 6619)
Posted 28 Apr 2020 by ProDigit
Post:
OpenCL 3.0 is on the way.
Supposedly OpenCL 1.2 with selective optimizations, rather than the full package like OpenCL 2.0

source


I would also not try to run 2 WUs at a time.
It seems a 2080 Ti (with mild power reduction to 180W) does a WU below 10 minutes.
I've ran them from 125 to 290W, and Asteroids seems to be able to tax these GPUs pretty much completely.
13) (Message 6618)
Posted 28 Apr 2020 by ProDigit
Post:
Currently, my RTX 2070 Super and 2080 Ti is running at full capacity, using GPU = 1 and CPU = 0.25.

The new WUs might have fixed the low GPU usage.

If a 2070 Super and 2080 Ti can be utilized 100%, a 1030 should as well.
14) (Message 6617)
Posted 27 Apr 2020 by ProDigit
Post:
I run Asteroids GPU (Nvidia RTX 2080Ti and 2070 Super) on a few machines, and found that the stock CPU setting of "0.01 CPU + 1 Nvidia GPU" is too low.

I think a CPU setting of 0.24 to 0.30 is much more accurate, in terms of fast CPU (3,75Ghz and up) and GPU (RTX or equivalent or higher); or slow CPU (2,50Ghz or below) and slow GPU (GTX or equivalent below this).

This will allow 1 core to be allocated per ~3-4 GPUs.

More testing is needed, but I believe the setting needs adjustment!
15) (Message 6615)
Posted 27 Apr 2020 by ProDigit
Post:

Superficially it looks like your math doesn't stack up. One 2080 is apparently 2 times faster than a 1060, and two of them are about 4 times faster. What did you expect ?



If I take Project Collatz as an example :

With one GPU NVidia GTX 1060 3GB : 1600 seconds for one task, 2,000,000 points per day.
With one NVidia RTX 2080 Ti : 130 seconds for one task, 19,000,000 points per day.

19000000/2000000=9.5 and 1600/130=12.3

For Collatz project, the NVidia RTX 2080 Ti is about 10 times faster than the NVidia GTX 1060.
So I'm very surprised that for Asteroids@home, it's only twice as fast ?
But maybe it's the numbers for Collatz that are abnormal !

Indeed, the theoretical power of RTX 2080 Ti is 13.45 TFlops and that of GTX 1060 is 4.4 TFlops.
13.45/4.4=3.
I really don't understand why there are such differences between BOINC projects ?

But I'm not a computer professional !


Each Project has it's own programmer to write the app, due to MANY differences there just no way to make this app just as fast as that app at another Project. One difference is the amount of data being processed, Collatz is looking for a result to a math problems, gpu's can zip thru those in no time. While Asteroids is also doing math stuff it's much more computationaly intense so takes much longer and is harder to optimize because of it.

The reason each Project has different programmers comes down to money and confidentially, project a doesn't want others stealing the way they do things so gets an in house person to do the programming while project b can afford to pay someone who has done it before so it's more optimized. BOTH work which is the whole point. Another difference is the money programmers want to do the app, some projects have the money to pay someone good while other projects only have the money to pay someone who can do it. Seti got Nvidia help writing theirs so it was highly optimized, Nvidia has not helped other projects to the same degree.

The collatz awards a quick return bonus.
That being said, a 2080Ti should be twice as fast as a 2060, not 1060!
I came here because I've been running a few batches of asteroids on 2080Tis and feel like I get WAY too little credit for it.
Granted, about 80Wus still need to be validated, but I feel we're not getting an equivalent PPD score on asteroids, vs on most other projects.

There might be an issue with the CPU not being fast enough to feed an rtx2080ti.