TT-Miner 2024.1.2 BLAKE3, KAWPOW, ETHASH, ETCHASH, EPIC, SHA512256D, SHA3D, ETI

[george2019]

well with cuda 10.1 hashrate is more or less same as with 10, so i'm using it in tt-miner, i haven't noticed any stability problems as well, with core oc it has higher hashrate at least on miner side, i leave memory 0, i had it 500+ but haven't noticed any hashrate increase, but i will try with memory +500 and lower core oc as well with latest tt-miner, now i'm testing with higher core oc and pill with TDP 70% and intensity 23, well with memory -502 i had some stability problem, so zero is best choice, i'm still on windows 10 1709 build, i will probably wait 19H1 build and install it in few months, maybe it has some improvements for mining as well with cuda 10.1 and WDDM 2.6 driver support
i used intensity 21 with t-rex miner and was getting best results, maybe i it will be better to use same intensity settings with tt-miner as well, i think 23 is too much with 4gb ram and celeron 1840 with 5 GPU, after i while hashrate dropped from 16mh/sec to 14.4mh/sec i will try 21 now, i think it should be optimal for my rig

[1714045971]

1714045971

[1714045971]

1714045971

[1714045971]

1714045971

[1714045971]

1714045971

[1714045971]

1714045971

[Divinity666]

Ok, I'm getting "out of virtual memory" even with -i 20... wtf, had no suck issue in prev. version, will try 19 now. The thin is only 41Gb out of 64Gb virtual memory are being used.

[george2019]

when you're testing different intensity settings it is better to restart system after each intensity change, otherwise you may have quite big hashrate drop, i'm testing it 22 now, it's either 21 or 22 for my system, as for pagefile i use only 32-33gb for both mtp and c29-c29s algos and i never had any problems with free space or memory:

https://i.imgur.com/ZSqbtJr.png that's for 4x1080 and one 1080Ti rig

you should test pool hashrate as well miner hashrate doesn't show whole story
with higher intensity maybe memory oc should increase pool hashrates as well, i will try it tommorow, at the moment intensity 22 is looking quite good, i haven't noticed higher pagefile usage since free space is same as before (around 11gb)

[Divinity666]

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...

[Juniormkl]

 TT-Miner 2.1.16 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

[Grim]

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

[dragonmike]

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.

[TrailingStop]

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?

[george2019]

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)

[Grim]

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.


 

[george2019]

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

[chrysophylax]

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.


 

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

Good to test if possible.

#crysx

[TrailingStop]

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.

[notsure85]

any numbers for 2080?

also linux version +1

[TrailingStop]

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?

[dragonmike]

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?

[TrailingStop]

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?

[stolarzz]

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

[ouray]

@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

[TrailingStop]

@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.