Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Mining (Altcoins)
Re: TT-Miner 2.2.2: ProgPoW, MTP, LYRA2V3, UBQHASH, MYR-GR Win/cuda9.2/10.0/10.1
by
TrailingStop
on 28/04/2019, 15:51:04 UTC
Quote from: c0mrade69 on April 28, 2019, 03:44:39 PM
Quote from: TrailingStop on April 28, 2019, 03:27:58 PM
Quote from: c0mrade69 on April 28, 2019, 03:16:24 PM
Quote from: TrailingStop on April 27, 2019, 06:09:36 PM
Quote from: c0mrade69 on April 27, 2019, 05:22:23 PM
Quote from: TrailingStop on April 27, 2019, 04:41:20 PM
Quote from: c0mrade69 on April 27, 2019, 04:20:51 PM

not sure what you think by last sentence sir..  I run it on +200/+200 and with MTP in config as posted above:
  
Code:
-A MTP-100 -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:x@zcoin-eu.mintpond.com:3000 --api-bind 127.0.0.1:4033


Just want to know if you mine with MTP algo when your OC settings worked. You already answer my question. Thanks. Let me know if TT works without OC.

Will let you know later, going to change it.

Wanted know if overclocking, increasing/decreasing of core/memory can affect the mining on this algo. Like when mining ETH +mem helps to increase speed or +core on equihash. I was thinking you as the dev would know about it something Smiley

unfortunately I do have not made a lot of test with OC. I noticed that PC does not have that impact on the hashrate for MTP as it shown on other algos. MTP is more core sensitive than mem - so you might want to play with core and leave mem untouched or even in the negative area. In the end you have to find the best settings for your system yourself since RIGs are very different and hard to compare - even if they run the same GPU.

You were right with the OC. Since I left it on default (no OC) rig runs smoothly. No crashing at all for 21 hours already. Got 4300 shares, 5 rejected only.

I'm just sorry that can't get higher hashrate, with OC I could get 10% more of it..

PS: when I got rejected share, its always gpu 1 or 3 (coincidence??) , with message:
Code:
23:29:23.452 POOL: Received new job#: 10cf
23:29:27.212 POOL: Error - Low difficulty. 0.00001859978871878651/1542(23)
23:29:27.231 GPU[3]: Rejected 441 ms. zcoin-eu.mintpond.com:3000 [51.68.181.133]

or

Code:
21:17:50.575 POOL: Received new job#: eef
21:17:50.591 POOL: difficulty down from 163.71 MH to 120.00 MH
21:17:59.139 POOL: Error - Low difficulty. 0.00001746934035415034/1831(23)
21:17:59.139 GPU[1]: Rejected 1593 ms. zcoin-eu.mintpond.com:3000 [51.68.181.133]

or

Code:
16:30:18.400 POOL: Error - MTP verify failed(20)
16:30:18.400 GPU[1]: Rejected 843 ms. zcoin-eu.mintpond.com:3000 [51.68.181.133]

Does the miner set different difficulty for each GPU? Or those cards were just unlucky because pool was changing difficulty at that time ?

Hi,

happy that your rig is stable now. Now is the correct time to start OC. Start with core - if you found the sweet point, switch over to mem (also try negative numbers for mem). You may also want to find the best value for the grid size/intensity, just try to add -i 15 or -i 16 and check if that gives you some more hashes.

Miner do not set difficulty - that is up to the pool you use. MintPond support vardiff, 2miners only a high static diff.

Rg the rejections you are right - if the Miner receives a new job or new (higher) diff when a new solution is found chances are high that this solutions gets rejected - I also noticed that your connection shows values for a full turn of the solution of 500 to 1500 ms. Maybe you can connect to a closer pool - or maybe your connection is not very fast???



Thank you for reply. I had to relocate my rig to other place, where internet pretty sucks. So that's most probably the reason for my rejected shares  Undecided . Didn't think about it before.

The pool has these options  (I dont understand them well):

Code:
Start Difficulty
Setting the starting difficulty will allow your miner to start mining quicker by setting the initial VarDiff difficulty closer to the optimal difficulty of your miner.

The best way to determine an optimal starting difficulty is to allow the VarDiff to run normally and see what difficulty it settles on after 30 minutes to an hour.

-p fYbWmE,sd=3.5

Minimum/Start Difficulty
This option sets both the minimum difficulty and the starting difficulty to the same value. The starting difficulty is the initial difficulty the VarDiff will start at and the minimum difficulty is the difficulty that the VarDiff will not go below.

-p fYbWmE,d=3.5

I remember I had similar settings on other miner before, I will try them and will see if it helps:

Code:
TT-Miner.exe -log -A MTP -P stratum+tcp://abcdefghasjdhaklsdjallkajdl.worker:x,d=4096,strict@zcoin-eu.mintpond.com:3000 --api-bind 127.0.0.1:4033
Code:
17:38:38.537 ****************** GPU information
17:38:38.537 Nvidia GeForce Driver-Version: 430.39
17:38:38.537 CUDA devices: 4
17:38:38.537 * #0 PCI 0:1 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.537 * #1 PCI 0:2 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 * #2 PCI 0:4 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 * #3 PCI 0:5 ASUS GeForce GTX 1070 Ti (6.1) CoreClk 139 MHz | MemClk 405 MHz | 8192 MB | SM: 19
17:38:38.538 ****************** Mining-Pool information
17:38:38.538 ID:0 - Primary pool: zcoin-eu.mintpond.com:3000
17:38:38.538 Wallet: abcdefghasjdhaklsdjallkajdl
17:38:38.538 Worker: worker:x
17:38:38.538 No backup pool defined
17:38:38.538 ****************** Algo information
17:38:38.538 Algo/Cuda detection: Auto detect
17:38:38.538 Algo/Cuda loaded: MTP for CUDA 10.10
17:38:38.539 ****************** Apply settings
17:38:38.539 Set process priority: default
17:38:38.539 Avg. performance timeframe: 2 minutes
17:38:38.539 Performance summary(seconds): 15 seconds
17:38:38.539 Performance summary(shares): disabled
17:38:38.539 Report Hashrate to pool: disabled
17:38:38.539 Use intensity: -
17:38:38.540 Use gridsize: -
17:38:38.540 API-Interface enabled. Listening on 1
17:38:38.542 ****************** Start mining
17:38:38.578 POOL: Connecting to zcoin-eu.mintpond.com:3000 - PoolID: 0
17:38:38.608 POOL: Connected to: zcoin-eu.mintpond.com:3000 - IP4: 51.68.181.133:3000, Protocol Stratum
17:38:38.639 POOL: Subscribed to zcoin-eu.mintpond.com:3000 - detected protocol: Stratum
17:38:38.671 POOL: Worker authorized: c0mrade
17:38:38.672 POOL: Message - Suggested min-difficulty accepted: 4096
17:38:38.672 POOL: Message - Strict mode enabled
17:38:38.685 POOL: Received new job#: 1f53
17:38:45.036 GPU[0]: 0.000 H/s  CClk:1.607 GHz MClk:157.03 MHz 43C 50% 37W 0.000 H/W [A0:R0 0.0%]  LastShare: -
17:38:45.037 GPU[1]: 0.000 H/s  CClk:1.607 GHz MClk:157.03 MHz 43C 50% 35W 0.000 H/W [A0:R0 0.0%]  LastShare: -
17:38:45.037 GPU[2]: 0.000 H/s  CClk:1.607 GHz MClk:157.03 MHz 40C 50% 35W 0.000 H/W [A0:R0 0.0%]  LastShare: -
17:38:45.038 GPU[3]: 0.000 H/s  CClk:1.607 GHz MClk:157.03 MHz 43C 50% 36W 0.000 H/W [A0:R0 0.0%]  LastShare: -
17:38:45.039 Rig-Speed[2 min]: 0.000 H/s 143W 0.000 H/W [A0:R0 0.0%] Uptime: 00:00:06  LastShare: -
17:38:46.124 Miner: GPU[0] use default intensity 14, Gridsize: 2432
17:38:46.125 Miner: GPU[1] use default intensity 14, Gridsize: 2432
17:38:46.126 Miner: GPU[2] use default intensity 14, Gridsize: 2432
17:38:46.126 Miner: GPU[3] use default intensity 14, Gridsize: 2432
17:38:46.127 POOL: difficulty up from 0.000 H to 268.44 MH

why is it trying to find difficulty if I set it before and it accepted it?

And want to ask you about intensity. Isnt it bad idea try to OC and change intensity at same time? Im thinking that intensity is kind of OC in fact. Maybe I should first try to change intensity, and try OC just after.. ?  Huh

The message to change the difficulty is just an information for you. The pool changes the diff and TT-Miner show it to you - so it is changed by the pool - not the miner.
I would first try to change intensity and find a good value for your rig. then I would OC - as the last thing.