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

[cost82el]

when linux?

[TrailingStop]

when linux?

I hope soon - within days. I'm working hard on it.

[TrailingStop]

yea what the hell 2.1.15 ProgPoW -50% hash 

Yes. Sorry. New release with a fix will come in an hour.
Sorry.

[TrailingStop]

New version 2.1.16

   - Reduced number of 'Duplicate shares' for ProgPoW algo
   - Fixed a bug that I added in version 2.1.15 that causes the hashrate to go down 50% for ProgPoW
   - Added intensity command line parameter
   - Added grid size command line parameter
   - Another Performance improvement for MTP

This version allow to set the intensity or the grid-size for each GPU in your rig. The miner shows the active intensity on mining start fo4r each GPU. You can overwrite this value using the -i (or -mi, -intensity) command line parameter. If you want to have a more detailed control over the grid-size you can use the intensity grid/grid-size command line parameter -ig (or -gs). The number you specify is the grid size. On mining start the miner shows you the active grid size. Take this value as a starting point for a more optimized setting for you system. See readme for more information - or ask me.

Let me know if you run into any issues or find any bug.

link to the miner: https://TradeProject.de/download/Miner/TT-Miner.zip

Thanks and happy mining.

[stolarzz]

New version 2.1.16

   - Reduced number of 'Duplicate shares' for ProgPoW algo
   - Fixed a bug that I added in version 2.1.15 that causes the hashrate to go down 50% for ProgPoW
   - Added intensity command line parameter
   - Added grid size command line parameter
   - Another Performance improvement for MTP

This version allow to set the intensity or the grid-size for each GPU in your rig. The miner shows the active intensity on mining start fo4r each GPU. You can overwrite this value using the -i (or -mi, -intensity) command line parameter. If you want to have a more detailed control over the grid-size you can use the intensity grid/grid-size command line parameter -ig (or -gs). The number you specify is the grid size. On mining start the miner shows you the active grid size. Take this value as a starting point for a more optimized setting for you system. See readme for more information - or ask me.

Let me know if you run into any issues or find any bug.

link to the miner: https://TradeProject.de/download/Miner/TT-Miner.zip

Thanks and happy mining.

Not enyough memory to run the algo, many rigs with this error on 2.1.16, previous version everything fine

[TrailingStop]

New version 2.1.16

   - Reduced number of 'Duplicate shares' for ProgPoW algo
   - Fixed a bug that I added in version 2.1.15 that causes the hashrate to go down 50% for ProgPoW
   - Added intensity command line parameter
   - Added grid size command line parameter
   - Another Performance improvement for MTP

This version allow to set the intensity or the grid-size for each GPU in your rig. The miner shows the active intensity on mining start fo4r each GPU. You can overwrite this value using the -i (or -mi, -intensity) command line parameter. If you want to have a more detailed control over the grid-size you can use the intensity grid/grid-size command line parameter -ig (or -gs). The number you specify is the grid size. On mining start the miner shows you the active grid size. Take this value as a starting point for a more optimized setting for you system. See readme for more information - or ask me.

Let me know if you run into any issues or find any bug.

link to the miner: https://TradeProject.de/download/Miner/TT-Miner.zip

Thanks and happy mining.

Not enyough memory to run the algo, many rigs with this error on 2.1.16, previous version everything fine

ah- maybe I set default intensity too high. Can you let me know which GPU and what algo please?

[stolarzz]

New version 2.1.16

   - Reduced number of 'Duplicate shares' for ProgPoW algo
   - Fixed a bug that I added in version 2.1.15 that causes the hashrate to go down 50% for ProgPoW
   - Added intensity command line parameter
   - Added grid size command line parameter
   - Another Performance improvement for MTP

This version allow to set the intensity or the grid-size for each GPU in your rig. The miner shows the active intensity on mining start fo4r each GPU. You can overwrite this value using the -i (or -mi, -intensity) command line parameter. If you want to have a more detailed control over the grid-size you can use the intensity grid/grid-size command line parameter -ig (or -gs). The number you specify is the grid size. On mining start the miner shows you the active grid size. Take this value as a starting point for a more optimized setting for you system. See readme for more information - or ask me.

Let me know if you run into any issues or find any bug.

link to the miner: https://TradeProject.de/download/Miner/TT-Miner.zip

Thanks and happy mining.

Not enyough memory to run the algo, many rigs with this error on 2.1.16, previous version everything fine

ah- maybe I set default intensity too high. Can you let me know which GPU and what algo please?

MTP, mostly 1070 non ti are crashing, but few 1080ti too.

EDIT. Yea looks like it's intensity, lovered it to 20 and they start working

[Alexios777]

Hi,
what is the max intensity that can be used?

[TrailingStop]

New version 2.1.16

   - Reduced number of 'Duplicate shares' for ProgPoW algo
   - Fixed a bug that I added in version 2.1.15 that causes the hashrate to go down 50% for ProgPoW
   - Added intensity command line parameter
   - Added grid size command line parameter
   - Another Performance improvement for MTP

This version allow to set the intensity or the grid-size for each GPU in your rig. The miner shows the active intensity on mining start fo4r each GPU. You can overwrite this value using the -i (or -mi, -intensity) command line parameter. If you want to have a more detailed control over the grid-size you can use the intensity grid/grid-size command line parameter -ig (or -gs). The number you specify is the grid size. On mining start the miner shows you the active grid size. Take this value as a starting point for a more optimized setting for you system. See readme for more information - or ask me.

Let me know if you run into any issues or find any bug.

link to the miner: https://TradeProject.de/download/Miner/TT-Miner.zip

Thanks and happy mining.

Not enyough memory to run the algo, many rigs with this error on 2.1.16, previous version everything fine

ah- maybe I set default intensity too high. Can you let me know which GPU and what algo please?

MTP, mostly 1070 non ti are crashing, but few 1080ti too.

EDIT. Yea looks like it's intensity, lovered it to 20 and they start working

That is strange. I run 1070 as well (non TI) and have no issues with higher intensity. Can you try to increase Virtual mem? The improvement may be worth it).
Please let me know if that works or not.

Thanks.

[stolarzz]

That is strange. I run 1070 as well (non TI) and have no issues with higher intensity. Can you try to increase Virtual mem? The improvement may be worth it).
Please let me know if that works or not.

Thanks.

It's already maxed out, i have small 120gb disk on the rigs and can't set it over 100gb It's 100gb virtual mem on 6 card rigs.

EDIT: Anyway it's a bit faster on -i 20 than 2.1.15 so great work with those two last versions, alreay you are the fastest on MTP. Enjoy your dev fee

[TrailingStop]

That is strange. I run 1070 as well (non TI) and have no issues with higher intensity. Can you try to increase Virtual mem? The improvement may be worth it).
Please let me know if that works or not.

Thanks.

It's already maxed out, i have small 120gb disk on the rigs and can't set it over 100gb It's 100gb virtual mem on 6 card rigs.

Ah. got it. I will set default back to 20.

[TrailingStop]

hashrate definitely improved , as for pool earnings i need at least one day to test on mintpond:

https://i.imgur.com/fkVaM2W.png

at the moment i'm running with cuda 10.1 command, are you planing to add intensity option on your miner, at the moment cpu usage is quite low and teamviewer running faster than cd 17 when mining mtp algo, your miner is first that broke 14mh.sec hashrate barrier on my 5 gpu rig, it's now faster than cd 17.0 with intensity 8 with same oc settings and pill, i think 2.1.15 build can even reach 15mh/sec with TDP 100% on my rig

Hi,

thanks for your suggestion. i added intensity to the new release. If you need more detailed control than intensity offers, you can use the grid-size command line parameter (-ig). Grid-size default is now 20 for MTP. Depending on your system, memory and GPU you may see another hashrate improvement if you increate intensity - of use grid-size parameter that fits your system best.

Let me know if that works for you or if you see any issues.

Thanks.

[george2019]

well default grid size and intensity working fine on my 5 gpu rig, i have 14.5mh/sec now, but what is maximum intensity setting 25? and what amount to put for grid size for 1080 and 1080Ti
lol with intensity 25 miner crashed (too low virtual memory) with intensity 24 it has some crazy hashrates 34mh/sec, i will find out optimal settings without too many rejects and stale shares that will work fine in 24 hour period

[Grim]

windows 7 has still worse performance with this release?

[TrailingStop]

windows 7 has still worse performance with this release?

I do not have Win7 at the moment. Are you on MTP? Please try to change intensity - for MTP try to add -i 19 or -i 21 to your command-line.

Please let me know if that helps.

Thanks.

[george2019]

well 24 is too much for my rig i will try to decrease msi gamer x 1080 core oc to from 170 to 150 since it crashed, some stale shares as well, i will try 23 now and report, meanwile some crazy zcoin price incease, around 80% in 24 hours, it's quite huge bullran, already 90% and almost 11$ at the moment from 5.5$, already 12$ and it goes higher and higher
https://i.imgur.com/ThGmBCN.png i sold it already and got around 0.00100 bitcoins i will sell 0.6 zcoins as well  since price is quite high at the moment, it's not bad at all after 1 week of mining
https://i.imgur.com/a1q9Yi8.png
i will test in 24 hours period and report back

[TrailingStop]

well 24 is too much for my rig i will try to decrease msi gamer x 1080 core oc to from 170 to 150 since it crashed, some stale shares as well, i will try 23 now and report, meanwile some crazy zcoin price incease, around 80% in 24 hours, it's quite huge bullran, already 90% and almost 11$ at the moment from 5.5$, already 12$ and it goes higher and higher
https://i.imgur.com/ThGmBCN.png

Enjoy

[dragonmike]

Yeah, let us know how you get on.
Are the latest versions benefiting from more core? Last time I used TT-miner I got the same hash by leaving core at stock and increasing mem and running the ETHlargement pill (which was actually better for power draw).

Also, is the miner faster using Cuda 10.1? I haven't actually upgraded yet...

[TrailingStop]

Yeah, let us know how you get on.
Are the latest versions benefiting from more core? Last time I used TT-miner I got the same hash by leaving core at stock and increasing mem and running the ETHlargement pill (which was actually better for power draw).

Also, is the miner faster using Cuda 10.1? I haven't actually upgraded yet...

Hi, I see a little higher hashrate with 10.1 than with 10. But that is with my 'low end' 1070. Not sure if that can be taken as general observation?

[Divinity666]

With -i 21 I kept running out of memory, so I lowered to 20, h\r dropped only by a little: 14.9 to 14.7 and it used to be 13.6 in previous release.

Hi, I see a little higher hashrate with 10.1 than with 10. But that is with my 'low end' 1070. Not sure if that can be taken as general observation?

Yeah, I've also noticed slight h\r improvement when updated 417.** to latest 419.35