Pages:
Author

Topic: TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 50. (Read 132259 times)

member
Activity: 566
Merit: 16
Hi
Can't find what exactly has been changed from 2.1.16 to 2.1.17?


Version 2.1.17 release

   - changed some functions of the miner so that the number of rejected shares will be reduced again - also for NiceHash pool.
         You might still see rejections under certain conditions - for example:
              - if a new job comes in while the miner send a solution for the old job
              - the connection to the pool was reestablished just before the solution was sent
   - set default intensity for MTP to 20.

To get the most out of your system you should always try other values (+- 1 of the current values the miner shows you on start) for intensity and for finetuning you should use grid-size value directly.

Let me know if you find any issue or have any problems.

Thanks - and happy mining.

member
Activity: 566
Merit: 16
I used Claymore's monitor app to check the miner. With CryptoDredge I am able to do just that using
this option: --api-type ccminer-tcp


>>>Do you want to have an web-frontend that shows you the current miner-status?
Yes and it does not work.  See below:

I configured my router to have one remote IP address for all individual port per miner.
With you rminer, I have this configured: --api-bind %APIaddress%:%APIport%

where as an example,
APIaddress = 123.456.789.012
APIport      =  99999

Using web-frontend, I would expect it works as under:
http://123.456.789.012:99999/

It does not work with your miner but it works using CryptoDredge.




got it. That cannot work. I do not have a http-server in the miner. just the api to control the status. Why dot you use one of the miner-control software?


>>>  Why dot you use one of the miner-control software?
Do you have one?
Last but not least, your miner is the best.   Smiley

Hi. Thanks - love to hear that Smiley

So there are a lot of GUI-miner control packages out there.

- Awesome Miner
- EthMonitoring

and a lot others. Just check this forum to find more. They will surely offer much more than you expect.

Thanks.
newbie
Activity: 42
Merit: 0
Hi
Can't find what exactly has been changed from 2.1.16 to 2.1.17?
newbie
Activity: 49
Merit: 0
I used Claymore's monitor app to check the miner. With CryptoDredge I am able to do just that using
this option: --api-type ccminer-tcp


>>>Do you want to have an web-frontend that shows you the current miner-status?
Yes and it does not work.  See below:

I configured my router to have one remote IP address for all individual port per miner.
With you rminer, I have this configured: --api-bind %APIaddress%:%APIport%

where as an example,
APIaddress = 123.456.789.012
APIport      =  99999

Using web-frontend, I would expect it works as under:
http://123.456.789.012:99999/

It does not work with your miner but it works using CryptoDredge.




got it. That cannot work. I do not have a http-server in the miner. just the api to control the status. Why dot you use one of the miner-control software?


>>>  Why dot you use one of the miner-control software?
Do you have one?
Last but not least, your miner is the best.   Smiley
member
Activity: 566
Merit: 16
I used Claymore's monitor app to check the miner. With CryptoDredge I am able to do just that using
this option: --api-type ccminer-tcp


>>>Do you want to have an web-frontend that shows you the current miner-status?
Yes and it does not work.  See below:

I configured my router to have one remote IP address for all individual port per miner.
With you rminer, I have this configured: --api-bind %APIaddress%:%APIport%

where as an example,
APIaddress = 123.456.789.012
APIport      =  99999

Using web-frontend, I would expect it works as under:
http://123.456.789.012:99999/

It does not work with your miner but it works using CryptoDredge.




got it. That cannot work. I do not have a http-server in the miner. just the api to control the status. Why dot you use one of the miner-control software?
member
Activity: 566
Merit: 16

@TrailingStop

I've been mining XZC using your miner for some time now.
The API does not work and I am unable to monitor remotely.

I switched to CryptoDredge just to test its API and it works.

Set up API same as your miner:
-b, --api-bind IP:port for the miner API, 0 disabled (default: 127.0.0.1:4068)

This is what your miner don't have. See example below:
 
--api-type Specify API type to use (default: ccminer-tcp)
    ccminer-tcp (TCP)
    ccminer-ws (WebSocket)
    off

I was wondering if you can add that into your next release. Please!
Thanks


Hi,

not sure what you are looking for? Do you want to have an web-frontend that shows you the current miner-status? Do you need WebSocket? TCP is already included.

Please give me some more details what you want to do.

Thanks.
newbie
Activity: 49
Merit: 0

@TrailingStop

I've been mining XZC using your miner for some time now.
The API does not work and I am unable to monitor remotely.

I switched to CryptoDredge just to test its API and it works.

Set up API same as your miner:
-b, --api-bind IP:port for the miner API, 0 disabled (default: 127.0.0.1:4068)

This is what your miner don't have. See example below:
 
--api-type Specify API type to use (default: ccminer-tcp)
    ccminer-tcp (TCP)
    ccminer-ws (WebSocket)
    off

I was wondering if you can add that into your next release. Please!
Thanks
newbie
Activity: 111
Merit: 0
any numbers for 2080?

also linux version +1

Hi, working on it. I own a Zotac 1070 only. My last test from today with PL 75%, core 0, mem 0, intentsity 20 -> 2.280 MH/s MTP @ NiceHash

maybe someone else can report the hashrate of an 2080 please?
Hmmm... I'm getting the same speeds on 1080s. Wonder what I'm doing wrong. Any ideas? Increasing core clocks doesn't seem to affect anything... Increasing intensity by 1 slows it down. I can't think that fine-tuning grid size would make a massive difference?
For 1080 use ethlargement pill, core +150 mem +700 it's going to up your hashrate to smth like 2.6mh/s
member
Activity: 566
Merit: 16
any numbers for 2080?

also linux version +1

Hi, working on it. I own a Zotac 1070 only. My last test from today with PL 75%, core 0, mem 0, intentsity 20 -> 2.280 MH/s MTP @ NiceHash

maybe someone else can report the hashrate of an 2080 please?
Hmmm... I'm getting the same speeds on 1080s. Wonder what I'm doing wrong. Any ideas? Increasing core clocks doesn't seem to affect anything... Increasing intensity by 1 slows it down. I can't think that fine-tuning grid size would make a massive difference?

Do you run the latest release? cuda 10.1? driver - I have 419.17 - and I put it for a test to 75% - now I switch back to 50% for development - having 1.950 MH/s

Do you have a 1070 to verify?
hero member
Activity: 1274
Merit: 556
any numbers for 2080?

also linux version +1

Hi, working on it. I own a Zotac 1070 only. My last test from today with PL 75%, core 0, mem 0, intentsity 20 -> 2.280 MH/s MTP @ NiceHash

maybe someone else can report the hashrate of an 2080 please?
Hmmm... I'm getting the same speeds on 1080s. Wonder what I'm doing wrong. Any ideas? Increasing core clocks doesn't seem to affect anything... Increasing intensity by 1 slows it down. I can't think that fine-tuning grid size would make a massive difference?
member
Activity: 566
Merit: 16
any numbers for 2080?

also linux version +1

Hi, working on it. I own a Zotac 1070 only. My last test from today with PL 75%, core 0, mem 0, intentsity 20 -> 2.280 MH/s MTP @ NiceHash

maybe someone else can report the hashrate of an 2080 please?
member
Activity: 139
Merit: 10
any numbers for 2080?

also linux version +1
member
Activity: 566
Merit: 16
Version 2.1.17 release

   - changed some functions of the miner so that the number of rejected shares will be reduced again - also for NiceHash pool.
         You might still see rejections under certain conditions - for example:
              - if a new job comes in while the miner send a solution for the old job
              - the connection to the pool was reestablished just before the solution was sent
   - set default intensity for MTP to 20.

To get the most out of your system you should always try other values (+- 1 of the current values the miner shows you on start) for intensity and for finetuning you should use grid-size value directly.

Let me know if you find any issue or have any problems.

Thanks - and happy mining.
legendary
Activity: 2940
Merit: 1091
--- ChainWorks Industries ---
MTP

Just noticed alot of people reporting exactly -50% hashrate on windows 7 (on discord).

ccminer mtp from djm seems to have the same win 7 "issue" as well as cryptodredge.


 Undecided

What are the links to the other miners? ...

Good to test if possible.

#crysx
jr. member
Activity: 83
Merit: 3
i'm testing nicehash mtp algo today and no more rejected shares, average hashrate was around 14.5mh/sec for my rig after 10 hours of mining, i will return direct mtp zcoin mining later when i receive 0.0010 bitcoin, just yesterday difficulty was too high because zcoin 110% bullran, i will test 2miners pool as well for 1 day to compare earnings vs mintpond, i returned old oc settings (maximum core oc memory 0 combination + pill) memory +500 doesn't show any improvements in pool hashrates
sr. member
Activity: 506
Merit: 252
MTP

Just noticed alot of people reporting exactly -50% hashrate on windows 7 (on discord).

ccminer mtp from djm seems to have the same win 7 "issue" as well as cryptodredge.


 Undecided
jr. member
Activity: 83
Merit: 3
well miner uses always around 33gb so i put 35gb, not all the algos need so much memory so i put 16gb as minimum amount, when mining mtp-c29 algo it increases when it's needed, otherwise there's much more free space left on system partition, there's nothing wrong with it if it works fine, i'm testing less core oc and + 500 memory oc combination now with TDP 70%, i also put d=5000 after password since starting mintpond difficulty is too small now when hashrates increased, with memory +500 miner need more time to show maximum hashrates, it started from 13.5mh, now it is already 14.5mh/sec after 15 minutes of mining, with core oc it shows highest hashrate at the beggining and hashrate starts dropping after few minutes, if pool will show good hashrates i will keep those setting since temps dropped (around 2 degrees celsius vs higher core oc + memory 0)
member
Activity: 566
Merit: 16
MTP mining:


win 10 cuda 10.1

1080ti, -i 21
3.5 MH/s


win 7 cuda 10.1

1080ti, -i 21
1.7 MH/s



so in win 7 about 50% less hash

Hi - can you please try to reduce intensity? I have no idea what the reason could be - just guessing?
hero member
Activity: 1274
Merit: 556
So far no h\r difference between -i 20 and 19, well mb 0.05Mhs drop it total, as for no "out of virtual memory" error - we shall see...
Just wanted to say (in case you and/or other people here didn't actually know it) that you need to set maximum AND minimum virtual memory values the same if you want them to actually stick. Setting only max value higher will not work.

Tried two different o/c settings on my 5x 1080 rig:

1) 85% PL, core +110, mem +0: 2.24MH/s per card @ 850W at the wall
2) 75% PL, core +0, mem +400, ETHlargement pill: 2.31MH/s per card @ 765W at the wall

No contest.
sr. member
Activity: 506
Merit: 252
MTP mining:


win 10 cuda 10.1

1080ti, -i 21
3.5 MH/s


win 7 cuda 10.1

1080ti, -i 21
1.7 MH/s



so in win 7 about 50% less hash
Pages:
Jump to: