[ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 33.

GreyGhost_rc

newbie

Activity: 9

Merit: 0

Quote from: du44 on October 31, 2018, 04:29:02 PM

Hello dear developers! I've installed this miner and it works perfectly stable, provides good hashrate. But dev fee is bearish... Please reduce it to 1-1.5% for cn8 and 1.5-2% for other algos. You will see - a lot of people will begun to use your miner, it's very important for community

You sure you don't want it for free? The dev fee is vindicated. Be glad they are putting in all the effort. Joh...

du44

full member

Activity: 251

Merit: 100

Hello dear developers! I've installed this miner and it works perfectly stable, provides good hashrate. But dev fee is bearish... Please reduce it to 1-1.5% for cn8 and 1.5-2% for other algos. You will see - a lot of people will begun to use your miner, it's very important for community

kerney666

member

Activity: 658

Merit: 86

Quote from: peteris-apse on October 31, 2018, 03:30:12 AM

good to know. wont bother updating minig soft for phi2. but on vega rig and cnv8 teamredminer kicks strong! power drain went down for liek few % and hashrate seems much higher - 12800 before 13800 now. Bet lets see ho stable this new miner is!

Hi!

For the sake of transparency: there is no increased hashrate for phi2 between the versions. The higher hashrate is because we are now presenting the raw hashrate _before_ dev fee, previously we thought we'd be helpful and show the net user hashrate after dev fee was excluded.

However, we grew tired of seeing our displayed numbers being compared to other miners with another 3% removed, so we changed it into the more standard way with the CNv8 release.

peteris-apse

jr. member

Activity: 98

Merit: 1

good to know. wont bother updating minig soft for phi2. but on vega rig and cnv8 teamredminer kicks strong! power drain went down for liek few % and hashrate seems much higher - 12800 before 13800 now. Bet lets see ho stable this new miner is!

todxx

member

Activity: 176

Merit: 76

New release versions 0.3.5 posted!

The most relevant change in this release for lyra2z and phi2 is that the GPU initialization has been changed to be sequential by default. This is to prevent problems that occur on some slower CPUs (such as celerons).
To make the miner perform a faster parallel init like in v0.3.4, use the option --init_style=3.

You can read the full changes in the main post, but the rest are mostly bug fixes for CNv8 related issues.

alucard20724

sr. member

Activity: 703

Merit: 272

Quote from: kerney666 on October 30, 2018, 12:16:35 PM

Quote from: alucard20724 on October 30, 2018, 09:09:33 AM

Quote from: todxx on October 30, 2018, 01:20:22 AM

New release v0.3.4 posted!

This version now includes cryptonight v8 support!
Also better reporting of GPU hashrates and reporting of submitted/accepted/rejected shares.
Please note that we have changed how we report GPU hashrates. Hashrates reported by the miner are now the full GPU hashrates. Previously hashrates reported were after dev fee deduction.

Since we expect a lot of questions and comments about cryptonight v8, we have created a new thread for it here.
Please post any cryptonight v8 related comments and questions in that thread.

are there parameters to be added to phi2? cause it would appear that 0.3.4 has killed the hashrate for phi2

That is surprising really, we haven't touched those kernels at all, should be exactly the same. On my Windows box, running the v0.3.2 vs 0.3.4 for a few mins with a 580+560+Vega 64, I get the following:

v0.3.2
[2018-10-30 13:10:12] Stats GPU 0 - phi2: 4.919Mh/s (4.320Mh/s) [2018-10-30 13:10:12] Stats GPU 1 - phi2: 2.034Mh/s (1.834Mh/s) [2018-10-30 13:10:12] Stats GPU 2 - phi2: 9.880Mh/s (8.948Mh/s) [2018-10-30 13:10:12] Stats Total - phi2: 16.832Mh/s (15.103Mh/s)

vs

v0.3.4
[2018-10-30 13:05:52] Stats GPU 0 - phi2: 5.076Mh/s, avg 5.073Mh/s, pool 5.089Mh/s 27/0 [2018-10-30 13:05:52] Stats GPU 1 - phi2: 2.087Mh/s, avg 2.114Mh/s, pool 1.926Mh/s 8/0 [2018-10-30 13:05:52] Stats GPU 2 - phi2: 10.18Mh/s, avg 10.18Mh/s, pool 12.08Mh/s 55/0 [2018-10-30 13:05:52] Stats Total - phi2: 17.34Mh/s, avg 17.36Mh/s, pool 19.10Mh/s

In v0.3.2 we displayed the net user hashrate (3% dev fee subtracted), this has changed in 0.3.4, we now display the raw hashrate. Adjusting for that change: 17.36 * 0.97 = 16.84, close enough to 16.832. So, I don't see a regression bug on my Windows box at least.

Can you give a quick description of your setup (os/driver/gpus) and what you're seeing?

Cheers, K

i think the problem was on my end... i lost network connectivity while benchmarking systems because one system locked up the network. I'll worry about it on the next release.

kerney666

member

Activity: 658

Merit: 86

Quote from: alucard20724 on October 30, 2018, 09:09:33 AM

Quote from: todxx on October 30, 2018, 01:20:22 AM

New release v0.3.4 posted!

This version now includes cryptonight v8 support!
Also better reporting of GPU hashrates and reporting of submitted/accepted/rejected shares.
Please note that we have changed how we report GPU hashrates. Hashrates reported by the miner are now the full GPU hashrates. Previously hashrates reported were after dev fee deduction.

Since we expect a lot of questions and comments about cryptonight v8, we have created a new thread for it here.
Please post any cryptonight v8 related comments and questions in that thread.

are there parameters to be added to phi2? cause it would appear that 0.3.4 has killed the hashrate for phi2

That is surprising really, we haven't touched those kernels at all, should be exactly the same. On my Windows box, running the v0.3.2 vs 0.3.4 for a few mins with a 580+560+Vega 64, I get the following:

v0.3.2
[2018-10-30 13:10:12] Stats GPU 0 - phi2: 4.919Mh/s (4.320Mh/s) [2018-10-30 13:10:12] Stats GPU 1 - phi2: 2.034Mh/s (1.834Mh/s) [2018-10-30 13:10:12] Stats GPU 2 - phi2: 9.880Mh/s (8.948Mh/s) [2018-10-30 13:10:12] Stats Total - phi2: 16.832Mh/s (15.103Mh/s)

vs

v0.3.4
[2018-10-30 13:05:52] Stats GPU 0 - phi2: 5.076Mh/s, avg 5.073Mh/s, pool 5.089Mh/s 27/0 [2018-10-30 13:05:52] Stats GPU 1 - phi2: 2.087Mh/s, avg 2.114Mh/s, pool 1.926Mh/s 8/0 [2018-10-30 13:05:52] Stats GPU 2 - phi2: 10.18Mh/s, avg 10.18Mh/s, pool 12.08Mh/s 55/0 [2018-10-30 13:05:52] Stats Total - phi2: 17.34Mh/s, avg 17.36Mh/s, pool 19.10Mh/s

In v0.3.2 we displayed the net user hashrate (3% dev fee subtracted), this has changed in 0.3.4, we now display the raw hashrate. Adjusting for that change: 17.36 * 0.97 = 16.84, close enough to 16.832. So, I don't see a regression bug on my Windows box at least.

Can you give a quick description of your setup (os/driver/gpus) and what you're seeing?

Cheers, K

alucard20724

sr. member

Activity: 703

Merit: 272

Quote from: todxx on October 30, 2018, 01:20:22 AM

New release v0.3.4 posted!

This version now includes cryptonight v8 support!
Also better reporting of GPU hashrates and reporting of submitted/accepted/rejected shares.
Please note that we have changed how we report GPU hashrates. Hashrates reported by the miner are now the full GPU hashrates. Previously hashrates reported were after dev fee deduction.

Since we expect a lot of questions and comments about cryptonight v8, we have created a new thread for it here.
Please post any cryptonight v8 related comments and questions in that thread.

are there parameters to be added to phi2? cause it would appear that 0.3.4 has killed the hashrate for phi2

N2DCRYPT

jr. member

Activity: 148

Merit: 5

Quote from: 9ville on October 30, 2018, 05:18:35 AM

Device number * is out of range.
What's the problem?

Try adding --platform=1 to your bat file.

9ville

newbie

Activity: 3

Merit: 0

Device number * is out of range.
What's the problem?

todxx

member

Activity: 176

Merit: 76

New release v0.3.4 posted!

This version now includes cryptonight v8 support!
Also better reporting of GPU hashrates and reporting of submitted/accepted/rejected shares.
Please note that we have changed how we report GPU hashrates. Hashrates reported by the miner are now the full GPU hashrates. Previously hashrates reported were after dev fee deduction.

Since we expect a lot of questions and comments about cryptonight v8, we have created a new thread for it here.
Please post any cryptonight v8 related comments and questions in that thread.

todxx

member

Activity: 176

Merit: 76

Quote from: 5BTC on October 27, 2018, 01:40:14 PM

Any idea when you expect the CNv8 release?

Have you tested it on Linux with multiple Vegas?

We're hoping to get CNv8 out in the next couple days.

We have not yet tested it on a linux system running multiple vegas, but we have tested it on a linux system with 7 x 470s and everything ran fine.
I would expect the same for a system with multiple Vegas.
Do note that CNv8 will require amdgpu-pro drivers version 18.30 or newer on linux for both Polaris and Vega cards. We do not initially plan to support CNv8 on ROCm.

5BTC

copper member

Activity: 48

Merit: 0

Any idea when you expect the CNv8 release?

Have you tested it on Linux with multiple Vegas?

kerney666

member

Activity: 658

Merit: 86

Quote from: Grumo on October 27, 2018, 10:34:59 AM

Team Red Miner version 0.3.3
[2018-10-27 17:33:43] Failed to initialize device number 0.

with 2 vega 56 under windows, latest drivers

Hi!

I would guess that you have two OpenCL platforms (zero and one). Unless specified on the command line, the miner checks for devices on platform zero. Please try adding "--platform=1" to your command line together with the rest of the parameters.

kerney666

member

Activity: 658

Merit: 86

Quote from: pbfarmer on October 27, 2018, 02:19:26 AM

Anyone able to get the api to respond in 0.3.3? Doesn't work for me...

Confirmed working with Awesome Miner and MinerStats. What is your command line, and do you connect from the same computer or some other machine on the network?

kerney666

member

Activity: 658

Merit: 86

Quote from: alucard20724 on October 26, 2018, 11:53:05 PM

was version 0.3.3 re-released?... github says it was released 2 days ago, however, i got it from github nine days ago.

There was an issue with the Linux tarball, the gzip compression wasn’t applied so people got “corrupt file” errors when trying to extract. It was fixed two days ago, hence the new timestamp.

ep690d

newbie

Activity: 28

Merit: 0

Quote from: pbfarmer on October 27, 2018, 02:19:26 AM

Anyone able to get the api to respond in 0.3.3? Doesn't work for me...

Doesn't work also for me by yesterday, i have problem with profit switching in Awesome Miner.

Grumo

member

Activity: 430

Merit: 22

Professional user

Team Red Miner version 0.3.3
[2018-10-27 17:33:43] Failed to initialize device number 0.

with 2 vega 56 under windows, latest drivers

pbfarmer

member

Activity: 340

Merit: 29

Anyone able to get the api to respond in 0.3.3? Doesn't work for me...

alucard20724

sr. member

Activity: 703

Merit: 272

was version 0.3.3 re-released?... github says it was released 2 days ago, however, i got it from github nine days ago.

Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 33. (Read 85791 times)