PTS and NRS GPU Miner PtsGPUz v0.5b for Windows(GTX 750Ti~820cpm)

Started by abc123, January 09, 2014, 10:29:02 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

abc123

PtsGPUz v0.5 now released.
Main change log:
PtsGPUz v0.5 (2014-03-13):
MD5 of PtsGPUz0.5.exe: 550e15f64ad9056d36e8a347336e58ec
MD5 of PtsGPUz0.5_x64.exe: 2286476b9d9399779b2fa9067566b7bd
1. Based on CUDA 6.0 RC (Release Candidate) now, release 64 bit version.
     Performance of NVIDIA GTX 750 Ti increased 92% (from 400cpm to 770cpm).
     Performance of NVIDIA GTX 780 Ti may also be improved, test needed.
2. Support specify AMD card by using "-da <num>" option.
3. Added collisions/round (c/round) display for more performance information.
4. Added fflush() after printf, now pipe output to text file by using
       ">> out.txt" at command line is possible.

aloec


abc123

Quote from: tazbox on February 19, 2014, 05:17:34 PM
Hello, how to mining only on one gpu.
I want mining on gpu 0 (nvidia) without mining on gpu 1 (amd).
Thanks for your advice. Please use PtsGPUz v0.3c, which don't support AMD cards.


tazbox

Hello, how to mining only on one gpu.

I want mining on gpu 0 (nvidia) without mining on gpu 1 (amd).

abc123

Quote from: lty616 on February 18, 2014, 06:01:51 PM
What do you mean they are different? you mean the way clpts 0.2.x calculates cpm is different to other miners? Please specify, thanks.
I means that he may find a very effective algorighm for cards like 280x.

lty616


I guess that the collision algorithm (not SHA512) in clpts 0.2.x is different from any other miners.
[/quote]

What do you mean they are different? you mean the way clpts 0.2.x calculates cpm is different to other miners? Please specify, thanks.

abc123

Quote from: lty616 on February 16, 2014, 05:27:39 PM
The Tahiti improved in clpts 0.2 is significant, which used to net1200+ (similar to 680/670) in its  v0.1 or any other miners now. I believe only clpts 0.2 makse a big step. If as you said, pts is designed by sha512, ,which should make no different, then I believe cuda has no reason behind AMD.
I guess that the collision algorithm (not SHA512) in clpts 0.2.x is different from any other miners.

Quote from: mwenyuan on February 17, 2014, 03:23:00 PM
hi @abc123,could you make your application writes running log to stdout, so i can use my watchdog script capture mining stats and restart mining process when cpm fall to 0.000 CPM accidently.
now i cannot pipe out anything from stdout or stderr when ptsgpuz running. Even start miner and pipe to text file with "> log.txt " is not working. Thank you!
Quote from: mwenyuan on February 18, 2014, 05:56:45 AM
and the first reply of this post may help:http://social.msdn.microsoft.com/Forums/vstudio/en-US/25c9a991-89df-4c70-b7d2-dd40eb35e235/redirecting-stdinstdoutstderr-for-windows-console?forum=vclanguage.
it's said if use printf and not calling fflush() on windows platform will make Pipe not working as expecting. i checked jhprotominer source code and find out it maybe the problem.
Thanks.  Without fflush(), it needs very long time to get something in the redirected "log.txt" file.

Quote from: zvs on February 18, 2014, 06:38:28 AM
Is there a way to run this on only device y, z, instead of device x, y, z?  I have a machine with r270, 5830, 5830...  clpts would be faster with the r270, but it crashes when I run ptsgpu (which starts mining on the 3 amd gpus)...   clpts gets 0 c/m for all my 1GB cards, not sure how you even run them...  (none of the 5830, 5850, 7770, 7790, or 7850 with 1GB works)
Not supported for AMD cards currently. The "-t", "-d" options only works for Nvidia cards now. Thanks for your advice.

Aselert

Hi guys,

I would like to establish a forecast of profitability. Is someone could help me?

For example, knowing how much is the monthly PTS mining profitability with the same RIG (cpm) speed? Taking into account the rising progressive difficulty. Even for an idea...?

Thank you! ;)

zvs

Quote from: abc123 on February 16, 2014, 08:19:06 AM
Quote from: lty616 on February 14, 2014, 03:58:03 PM
My friend's R9 280X can have 3100/3500 (default/OC) cpm on clpts-v0.2.2, and my gtx690 has 2200 cpm in total. I believe this means AMD now is much faster in SHA 512, single chip beats my two. clpts also asks for 2 threads for each chip like your miner, apparently, it is much more efficient and optimized.
Check this post https://bitsharestalk.org/index.php?topic=2598.0
Thanks for the information you provided. I don't have a R9 280x just now, on my HD7850 2GB, clpts-v0.2.2 is ~15% faster displayed, ~10% faster net than PtsGPUz v0.4c, which net performance is 840 cpm.
===================
Preliminary test result, only on HD6670 1GB:
AMD HD6670 1GB, test using AMD Catalyst 13.12, Windows 8 x64, G1610 CPU:
1. ominer 0.8, 425 cpm, fixed to upcpu, pool fee 2%, net performance user gets: 417 cpm;
2. PtsGPUz 0.4c, 380 cpm, pool fee 3% at ptspool.com, net performance user gets: 368 cpm;
3. ominer 0.9 preview 2, 336 cpm, fixed to upcpu, pool fee 2%, net performance user gets: 329 cpm;
4. clpts 0.2.2, 218 cpm, fixed to ypool.net, miner fee 5%, pool fee 5%, net performance user gets: 197 cpm.
Note: clpts 0.2.2 seem to be the fastest on AMD cards with 2GB or more video memory, but slowest on cards with 1GB memory.

Is there a way to run this on only device y, z, instead of device x, y, z?  I have a machine with r270, 5830, 5830...  clpts would be faster with the r270, but it crashes when I run ptsgpu (which starts mining on the 3 amd gpus)...   clpts gets 0 c/m for all my 1GB cards, not sure how you even run them...  (none of the 5830, 5850, 7770, 7790, or 7850 with 1GB works)
Pls to join [url=https://primedice.com/?ref=Zvs]Primedice 3[/url] and frolic about merrily whilst gambling awe-inspiring quantities of bitcoins. The power of [url=http://nogleg.com/exorcism.jpg]Christ[/url] compels you.

I have a dogecoin p2pool at [url=http://nogleg.com:9555]Nogleg[/url].

mwenyuan

and the first reply of this post may help:http://social.msdn.microsoft.com/Forums/vstudio/en-US/25c9a991-89df-4c70-b7d2-dd40eb35e235/redirecting-stdinstdoutstderr-for-windows-console?forum=vclanguage.

it's said if use printf and not calling fflush() on windows platform will make Pipe not working as expecting. i checked jhprotominer source code and find out it maybe the problem.

mwenyuan

hi @abc123,could you make your application writes running log to stdout, so i can use my watchdog script capture mining stats and restart mining process when cpm fall to 0.000 CPM accidently.

now i cannot pipe out anything from stdout or stderr when ptsgpuz running. Even start miner and pipe to text file with "> log.txt " is not working.

Thank you!

lty616

The Tahiti improved in clpts 0.2 is significant, which used to net1200+ (similar to 680/670) in its  v0.1 or any other miners now. I believe only clpts 0.2 makse a big step. If as you said, pts is designed by sha512, ,which should make no different, then I believe cuda has no reason behind AMD.

abc123

Quote from: lty616 on February 14, 2014, 03:58:03 PM
My friend's R9 280X can have 3100/3500 (default/OC) cpm on clpts-v0.2.2, and my gtx690 has 2200 cpm in total. I believe this means AMD now is much faster in SHA 512, single chip beats my two. clpts also asks for 2 threads for each chip like your miner, apparently, it is much more efficient and optimized.
Check this post https://bitsharestalk.org/index.php?topic=2598.0
Thanks for the information you provided. I don't have a R9 280x just now, on my HD7850 2GB, clpts-v0.2.2 is ~15% faster displayed, ~10% faster net than PtsGPUz v0.4c, which net performance is 840 cpm.
===================
Preliminary test result, only on HD6670 1GB:
AMD HD6670 1GB, test using AMD Catalyst 13.12, Windows 8 x64, G1610 CPU:
1. ominer 0.8, 425 cpm, fixed to upcpu, pool fee 2%, net performance user gets: 417 cpm;
2. PtsGPUz 0.4c, 380 cpm, pool fee 3% at ptspool.com, net performance user gets: 368 cpm;
3. ominer 0.9 preview 2, 336 cpm, fixed to upcpu, pool fee 2%, net performance user gets: 329 cpm;
4. clpts 0.2.2, 218 cpm, fixed to ypool.net, miner fee 5%, pool fee 5%, net performance user gets: 197 cpm.
Note: clpts 0.2.2 seem to be the fastest on AMD cards with 2GB or more video memory, but slowest on cards with 1GB memory.