First steps in GPU GIMPS

[Mark Rose]

I'm afraid I can't help more as I've never used Misfit personally (it's only for Windows).

[Jurzal]

All working now like a charm, automatic fetching and automatic uploading, while hidden in system tray :)
Thanks all for helping out!

Screenshot with current progress, some tasks have been chugged out. Almost 30k GHz days already done. ^^

[Andrew Usher]

That's great, but did you actually want to do only TF? It seems no one asked, but if you just want to do the most to help the project, primality tests on your CPU may still be the better choice.

[VBCurtis]

Originally Posted by Andrew Usher

That's great, but did you actually want to do only TF? It seems no one asked, but if you just want to do the most to help the project, primality tests on your CPU may still be the better choice.

This looks like lousy advice. Please explain your reasoning.

You used "may still be", which suggests you actually don't know if your own advice is useful- so why did you even post?

[kriesel]

Amen. It takes a minute or two to learn what Jurzal or any specific user has been doing in the way of primality testing, providing forum id = primenet id. (Instead of guessing, wrongly, and offering poor and vague advice.)
See also https://mersenneforum.org/showpost.p...2&postcount=1;
https://www.mersenne.org/report_LL/?user_id=jurzal 8 in LL DC 68M this year
https://www.mersenne.org/report_PRP/?user_id=jurzal 2 in 116M this year
(I don't know if he's also done P-1; there's no P-1 results report for other users, equivalent to the preceding.)

Thank you Jurzal for your contributions, and carry on. TF is the best use for the specific GPU model listed in post one.
(But feel free to experiment/play with other computation types on it too.) And TF or whatever on the GPU will have little or no impact on primality testing or P-1 on the CPU. It's standard to run both simultaneously. Most of my systems run apps on CPU and on GPU(s) simultaneously; in most cases some mix of Mlucas, prime95, gpuowl, mfaktc, mmff. And some of them have Google Colab free cloud computing sessions in a web browser also. Most of the throughput is provided by the GPUs.

[Jurzal]

Originally Posted by Andrew Usher

That's great, but did you actually want to do only TF? It seems no one asked, but if you just want to do the most to help the project, primality tests on your CPU may still be the better choice.

CPU is chugging too, 2 workers, 6 cores each from 5900X :)

[Jurzal]

Originally Posted by kriesel

Amen. It takes a minute or two to learn what Jurzal or any specific user has been doing in the way of primality testing, providing forum id = primenet id. (Instead of guessing, wrongly, and offering poor and vague advice.)
See also https://mersenneforum.org/showpost.p...2&postcount=1;
https://www.mersenne.org/report_LL/?user_id=jurzal 8 in LL DC 68M this year
https://www.mersenne.org/report_PRP/?user_id=jurzal 2 in 116M this year
(I don't know if he's also done P-1; there's no P-1 results report for other users, equivalent to the preceding.)

Thank you Jurzal for your contributions, and carry on. TF is the best use for the specific GPU model listed in post one.
(But feel free to experiment/play with other computation types on it too.) And TF or whatever on the GPU will have little or no impact on primality testing or P-1 on the CPU. It's standard to run both simultaneously. Most of my systems run apps on CPU and on GPU(s) simultaneously; in most cases some mix of Mlucas, prime95, gpuowl, mfaktc, mmff. And some of them have Google Colab free cloud computing sessions in a web browser also. Most of the throughput is provided by the GPUs.

Thanks! I haven't done P-1 yet. My settings in GIMPS are set to give me assignments that GIMPS think are most useful and I let it be as is.

[Andrew Usher]

Thanks; I was just asking, but that answers the question. I'd be afraid to run both a CPU and GPU continuously like that, due to possible power or cooling overload; but I might be just out of date as usual.

I see you've found some factors, too; that, rather than GHz-days, is the true measure of factoring production.

Finally, you might get some P-1 work if you increase your prime95 memory allocation enough, as P-1 uses lots of memory, but leaving it this way is also fine.

[kracker]

Originally Posted by Andrew Usher

Thanks; I was just asking, but that answers the question. I'd be afraid to run both a CPU and GPU continuously like that, due to possible power or cooling overload; but I might be just out of date as usual.

I see you've found some factors, too; that, rather than GHz-days, is the true measure of factoring production.

Finally, you might get some P-1 work if you increase your prime95 memory allocation enough, as P-1 uses lots of memory, but leaving it this way is also fine.

I'm struggling to not say something a lot more harsh, but the amount of pure assumptions you so often make along with you confidently accepting those assumptions as fact... is honestly astounding to me.

Contributors have(hopefully) the freedom of crunching what/how they want. Maybe given time, they can try different things through experimentation or suggestions from others... but at the end of the day, that's their choice and we're lucky to have them here.

[Jurzal]

Originally Posted by Andrew Usher

Thanks; I was just asking, but that answers the question. I'd be afraid to run both a CPU and GPU continuously like that, due to possible power or cooling overload; but I might be just out of date as usual.

I see you've found some factors, too; that, rather than GHz-days, is the true measure of factoring production.

Finally, you might get some P-1 work if you increase your prime95 memory allocation enough, as P-1 uses lots of memory, but leaving it this way is also fine.

Both CPU and GPU are undervolted, fitted into large, airflow case with 5x140 mm inflow fans giving enough airflow.
CPU is lapped, with 360 mm AIO and push/pull fan config. GPU is ASUS Rog Strix OC, it is so overbuilt, that it sits at 45-47c while chugging TF. CPU sitting average at 64-66c. Total power consumption from the wall is around 450-500w, temperatures are not a problem. Memory allocation is 24 GB from 32 available. So far it uses only a fraction of that, for PRP.

Problem thou, what I notice now is with larger PRP calculations, proof file is getting rewritten all the time on my SSD, putting a heavy toll on it's life longevity. Lot of Terabytes written on that SSD already from P95. In 9 hours, 43 GB written on the SSD, I am using SN850 1 TB drive. It is rated for 600 TBW. I will monitor the SSD usage for a bit, but if the SSD will get destroyed like that, I may opt out of PRP work for CPU.

[Mark Rose]

Originally Posted by Jurzal

Both CPU and GPU are undervolted, fitted into large, airflow case with 5x140 mm inflow fans giving enough airflow.
CPU is lapped, with 360 mm AIO and push/pull fan config. GPU is ASUS Rog Strix OC, it is so overbuilt, that it sits at 45-47c while chugging TF. CPU sitting average at 64-66c. Total power consumption from the wall is around 450-500w, temperatures are not a problem. Memory allocation is 24 GB from 32 available. So far it uses only a fraction of that, for PRP.

Problem thou, what I notice now is with larger PRP calculations, proof file is getting rewritten all the time on my SSD, putting a heavy toll on it's life longevity. Lot of Terabytes written on that SSD already from P95. In 9 hours, 43 GB written on the SSD, I am using SN850 1 TB drive. It is rated for 600 TBW. I will monitor the SSD usage for a bit, but if the SSD will get destroyed like that, I may opt out of PRP work for CPU.

If you want to save power, setting a lower power limit on your GPU is useful. I cap my 270 watt 3070s at 200 watts and get 95% of the performance.

You have a good amount of RAM to run P-1 work.

600000 / (43 * (24/9)) / 365 = 14.3 years