T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 71.

Chovus

newbie

Activity: 8

Merit: 0

Quote from: Xazax310 on December 06, 2018, 08:25:15 AM

Quote from: Chovus on December 06, 2018, 06:34:45 AM

Does anyone tested Hashrate of nVidia 1060 on algo x21s T-rex 0.8.5?

I got 6.15 MHS per card or totaly 31.1Mhs per rig (5 cards)?

Used Cuda 9.2 and driver 396.54 on Linux. Anyone else tested?

Thanks

I get about 5.9Mh/s~ with 70% PL and +125 core using Cuda 10, windows and t-rex 8.5

Quote from: Mr.Spider703 on December 06, 2018, 06:41:54 AM

Quote from: Chovus on December 06, 2018, 06:34:45 AM

Does anyone tested Hashrate of nVidia 1060 on algo x21s T-rex 0.8.5?

I got 6.15 MHS per card or totaly 31.1Mhs per rig (5 cards)?

Used Cuda 9.2 and driver 396.54 on Linux. Anyone else tested?

Thanks

win 10
drivers 416.xx
7.5 Mh
core +100 mem 0 PL 95

I forgot to OC core clock, it was left cor -200 and mem +200 PL 75.
Now with cor+200 mem 0 PL 75 ... I got 7.3 MHS thanks

Xazax310

member

Activity: 246

Merit: 24

Quote from: Chovus on December 06, 2018, 06:34:45 AM

Does anyone tested Hashrate of nVidia 1060 on algo x21s T-rex 0.8.5?

I got 6.15 MHS per card or totaly 31.1Mhs per rig (5 cards)?

Used Cuda 9.2 and driver 396.54 on Linux. Anyone else tested?

Thanks

I get about 5.9Mh/s~ with 70% PL and +125 core using Cuda 10, windows and t-rex 8.5

Mr.Spider703

member

Activity: 392

Merit: 27

http://radio.r41.ru

Quote from: Chovus on December 06, 2018, 06:34:45 AM

Does anyone tested Hashrate of nVidia 1060 on algo x21s T-rex 0.8.5?

I got 6.15 MHS per card or totaly 31.1Mhs per rig (5 cards)?

Used Cuda 9.2 and driver 396.54 on Linux. Anyone else tested?

Thanks

win 10
drivers 416.xx
7.5 Mh
core +100 mem 0 PL 95

Chovus

newbie

Activity: 8

Merit: 0

Does anyone tested Hashrate of nVidia 1060 on algo x21s T-rex 0.8.5?

I got 6.15 MHS per card or totaly 31.1Mhs per rig (5 cards)?

Used Cuda 9.2 and driver 396.54 on Linux. Anyone else tested?

Thanks

minertalk

jr. member

Activity: 38

Merit: 6

X22i - Suqa Coin
T-Rex NVIDIA GPU miner v0.8.5 - [CUDA v10.0]
NVIDIA Driver v417.22

Code:

20181205 05:36:13 Shares/min: 6.322 (average 10.525)
20181205 05:36:13 Uptime: 47 mins 58 secs
20181205 05:36:14 [ OK ] 506/506 - 11.20 MH/s, 87ms
20181205 05:36:32 [ OK ] 507/507 - 11.21 MH/s, 88ms
20181205 05:36:32 [ OK ] 508/508 - 11.21 MH/s, 88ms
20181205 05:36:35 [ OK ] 509/509 - 11.21 MH/s, 88ms
20181205 05:36:43 [ OK ] 510/510 - 11.22 MH/s, 87ms
20181205 05:36:43 GPU #0: ASUS GTX 1070 Ti - 11.22 MH/s, [T:52C, P:113W, F:50%,
E:98kH/W]
20181205 05:36:43 Shares/min: 6.026 (average 10.52)
20181205 05:36:43 Uptime: 48 mins 28 secs
20181205 05:36:45 [ OK ] 511/511 - 11.22 MH/s, 88ms
20181205 05:36:50 [ OK ] 512/512 - 11.22 MH/s, 87ms
20181205 05:36:55 [ OK ] 513/513 - 11.22 MH/s, 86ms
20181205 05:36:57 [ OK ] 514/514 - 11.22 MH/s, 87ms
20181205 05:36:58 [ OK ] 515/515 - 11.22 MH/s, 87ms
20181205 05:36:58 GPU #0: ASUS GTX 1070 Ti - 11.22 MH/s, [T:52C, P:115W, F:50%,
E:98kH/W]
20181205 05:36:58 Shares/min: 6.372 (average 10.57)
20181205 05:36:58 Uptime: 48 mins 43 secs
20181205 05:37:25 [ OK ] 516/516 - 11.22 MH/s, 86ms
20181205 05:37:29 [ OK ] 517/517 - 11.22 MH/s, 86ms
20181205 05:38:01 [ OK ] 518/518 - 11.22 MH/s, 87ms
20181205 05:38:04 [ OK ] 519/519 - 11.22 MH/s, 88ms
20181205 05:38:10 [ OK ] 520/520 - 11.22 MH/s, 87ms
20181205 05:38:10 GPU #0: ASUS GTX 1070 Ti - 11.22 MH/s, [T:52C, P:111W, F:50%,
E:98kH/W]
20181205 05:38:10 Shares/min: 5.907 (average 10.414)
20181205 05:38:10 Uptime: 49 mins 55 secs
20181205 05:38:35 [ OK ] 521/521 - 11.21 MH/s, 87ms
20181205 05:39:06 [ OK ] 522/522 - 11.21 MH/s, 88ms
20181205 05:39:07 [ OK ] 523/523 - 11.21 MH/s, 87ms
20181205 05:39:17 [ OK ] 524/524 - 11.20 MH/s, 89ms
20181205 05:39:25 x22i block 48010, diff 13281.859
20181205 05:39:26 [ OK ] 525/525 - 11.20 MH/s, 87ms
20181205 05:39:26 GPU #0: ASUS GTX 1070 Ti - 11.20 MH/s, [T:52C, P:100W, F:50%,
E:98kH/W]
20181205 05:39:26 Shares/min: 5.968 (average 10.256)
20181205 05:39:26 Uptime: 51 mins 11 secs
20181205 05:39:30 [ OK ] 526/526 - 11.19 MH/s, 87ms

conclusion: T-rex 0.7.4 8MH/s >>> T-rex 0.8.5 11 Mh/s whats next ? T-rex 1.0.0 20 MH/s ?...to the moon

Xazax310

member

Activity: 246

Merit: 24

Quote from: tomaroc on December 03, 2018, 04:37:34 PM

hi
My hashrate on T-Rex 0.8.4 CUDA 10, 416.34 drivers (windows 10)
The x22i (SUQA) algorithm
OC:
Power Limit 65% for gtx 980ti 70% for gtx 1070
core +160
memory + 500

Code:

20181203 22:24:52 GPU #0: Gigabyte GTX 1070 - 9554.61 kH/s, [T:57C, P:79W, F:36%, E:76kH/W]
20181203 22:24:52 GPU #1: Gigabyte GTX 1070 - 9677.11 kH/s, [T:57C, P:97W, F:34%, E:77kH/W]
20181203 22:24:52 GPU #2: Gigabyte GTX 980 Ti - 8509.75 kH/s, [T:66C, P:181W, F:48%, E:47kH/W]
20181203 22:24:52 GPU #3: Gigabyte GTX 980 Ti - 8823.89 kH/s, [T:63C, P:195W, F:40%, E:46kH/W]
20181203 22:24:52 GPU #4: Zotac GTX 980 Ti - 9131.33 kH/s, [T:61C, P:195W, F:11%, E:47kH/W]
20181203 22:24:52 Shares/min: 19.242 (average 10.857)
20181203 22:24:52 Uptime: 22 hours 54 mins
20181203 22:25:00 [ OK ] 14919/14951 - 45.70 MH/s, 123ms
20181203 22:25:04 [ OK ] 14920/14952 - 45.66 MH/s, 111ms
20181203 22:25:06 [ OK ] 14921/14953 - 45.66 MH/s, 109ms

Someone tried the latest NVIDIA 417.22 drivers (released December 3, 2018) - work better ?

Don't need memory overclock for SUQA just FYI just core. Hashrates looks fine doubt 417 would change anything besides your BF V experience!.

Xazax310

member

Activity: 246

Merit: 24

Very nice! I've been getting constant improvements in x22i every release! v8.4 i saw 2-3 mh/s(overall) with my 13 1060 rig hoping to see another 3mh/s!

trexminer

member

Activity: 283

Merit: 63

T-Rex 0.8.5 released.

Performance improvements: x22i +5%

tomaroc

newbie

Activity: 55

Merit: 0

hi
My hashrate on T-Rex 0.8.4 CUDA 10, 416.34 drivers (windows 10)
The x22i (SUQA) algorithm
OC:
Power Limit 65% for gtx 980ti 70% for gtx 1070
core +160
memory + 500

Code:

20181203 22:24:52 GPU #0: Gigabyte GTX 1070 - 9554.61 kH/s, [T:57C, P:79W, F:36%, E:76kH/W]
20181203 22:24:52 GPU #1: Gigabyte GTX 1070 - 9677.11 kH/s, [T:57C, P:97W, F:34%, E:77kH/W]
20181203 22:24:52 GPU #2: Gigabyte GTX 980 Ti - 8509.75 kH/s, [T:66C, P:181W, F:48%, E:47kH/W]
20181203 22:24:52 GPU #3: Gigabyte GTX 980 Ti - 8823.89 kH/s, [T:63C, P:195W, F:40%, E:46kH/W]
20181203 22:24:52 GPU #4: Zotac GTX 980 Ti - 9131.33 kH/s, [T:61C, P:195W, F:11%, E:47kH/W]
20181203 22:24:52 Shares/min: 19.242 (average 10.857)
20181203 22:24:52 Uptime: 22 hours 54 mins
20181203 22:25:00 [ OK ] 14919/14951 - 45.70 MH/s, 123ms
20181203 22:25:04 [ OK ] 14920/14952 - 45.66 MH/s, 111ms
20181203 22:25:06 [ OK ] 14921/14953 - 45.66 MH/s, 109ms

Someone tried the latest NVIDIA 417.22 drivers (released December 3, 2018) - work better ?

Juniormkl

newbie

Activity: 155

Merit: 0

T-Rex 0.8.4 (Windows/Linux) added to https://www.minermonitoring.com/

Join our discord https://discord.gg/aGGaeqq

also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark

trexminer

member

Activity: 283

Merit: 63

Quote from: 12x_1080_Ti on December 02, 2018, 03:46:24 PM

Hello Dear Dev,
Command line arguments must be always override the default JSON configuration.
Fairly common practice in the mining software development.
Standardization with respect to the quality and usability are very good
We (a group of miners) would like to use your program, but it is not convenient.
config priority - It's not nearly as handy as we thought it'd be.
so we are using another program for now...

Hi 12x_1080_Ti, command line arguments do override config file parameters. Could you show an example of how you tried to use config files along with cmd arguments and it didn't work as expected? Maybe there's a bug we need to fix, but like I said cmd line arguments take precedence over config parameters in T-Rex.

milfstick

newbie

Activity: 41

Merit: 0

Quote from: VVoutje on December 02, 2018, 05:04:33 PM

Quote from: milfstick on December 02, 2018, 04:02:45 PM

Quote from: VVoutje on December 02, 2018, 05:16:01 AM

Quote from: milfstick on December 01, 2018, 06:38:44 PM

Anyone know what this error is about? as soon as it goes to dev pool this happens

Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.

miner restarts Huh

It did happens sometimes to me if memory overclock or gpu overclock settings or intensity settings were setup to high. I don't know your mining hardware but start with no overclocking and intensity on 19 and try again.

Yeah thanks ive increased the power from 65 to 70 and it seems ok for now well for the 2hrs anyway. The overclock is 100 on core and 300 on mem (1070ti)

On my GTX1070 core on +75 just stays stable on x16r algo, mem isn't used for that algo so is set to -400, in linux you set a power limit in Watt witch I did on 160W (Max=200)

sorry i forgot to mention what algo i was using .. Im mining ritocoin so im using x21s. S ive been stable for over 3 hrs now not sure if it was the sofware update or the power increase. Happy so far...... good work on this Dev Grin

VVoutje

newbie

Activity: 8

Merit: 0

Quote from: milfstick on December 02, 2018, 04:02:45 PM

Quote from: VVoutje on December 02, 2018, 05:16:01 AM

Quote from: milfstick on December 01, 2018, 06:38:44 PM

Anyone know what this error is about? as soon as it goes to dev pool this happens

Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.

miner restarts Huh

It did happens sometimes to me if memory overclock or gpu overclock settings or intensity settings were setup to high. I don't know your mining hardware but start with no overclocking and intensity on 19 and try again.

Yeah thanks ive increased the power from 65 to 70 and it seems ok for now well for the 2hrs anyway. The overclock is 100 on core and 300 on mem (1070ti)

On my GTX1070 core on +75 just stays stable on x16r algo, mem isn't used for that algo so is set to -400, in linux you set a power limit in Watt witch I did on 160W (Max=200)

milfstick

newbie

Activity: 41

Merit: 0

Quote from: VVoutje on December 02, 2018, 05:16:01 AM

Quote from: milfstick on December 01, 2018, 06:38:44 PM

Anyone know what this error is about? as soon as it goes to dev pool this happens

Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.

miner restarts Huh

It did happens sometimes to me if memory overclock or gpu overclock settings or intensity settings were setup to high. I don't know your mining hardware but start with no overclocking and intensity on 19 and try again.

Yeah thanks ive increased the power from 65 to 70 and it seems ok for now well for the 2hrs anyway. The overclock is 100 on core and 300 on mem (1070ti)

12x_1080_Ti

newbie

Activity: 5

Merit: 0

Hello Dear Dev,
Command line arguments must be always override the default JSON configuration.
Fairly common practice in the mining software development.
Standardization with respect to the quality and usability are very good
We (a group of miners) would like to use your program, but it is not convenient.
config priority - It's not nearly as handy as we thought it'd be.
so we are using another program for now...

lordnitro

member

Activity: 104

Merit: 10

Can you add x20r please?

VVoutje

newbie

Activity: 8

Merit: 0

Quote from: milfstick on December 01, 2018, 06:38:44 PM

Anyone know what this error is about? as soon as it goes to dev pool this happens

Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.

miner restarts Huh

It did happens sometimes to me if memory overclock or gpu overclock settings or intensity settings were setup to high. I don't know your mining hardware but start with no overclocking and intensity on 19 and try again.

milfstick

newbie

Activity: 41

Merit: 0

Anyone know what this error is about? as soon as it goes to dev pool this happens

Error cant find share with device [id=2, GPU #2], cuda exception in [Algorithm::find_shares, 191] an illegal memory access was encountered.

miner restarts Huh

ctp9

jr. member

Activity: 52

Merit: 5

What's everyone's most ideal / optimal overclocking (and power limit) settings for x16r (Ravencoin)? As well - what intensity are you using and which GPUs?

VVoutje

newbie

Activity: 8

Merit: 0

For sure, great work tnx for that.

Topic: T-Rex 0.26.8 ETHW, ETC (+dual mining) GPU miner - page 71. (Read 174982 times)