 Show Posts
|
|
Pages: « 1 [2] 3 4 5 6 »
|
|
Im on 13.5c/kw, my rigs are working all the time from 2017. They were switched off only one month in December 2018.
I'm operating only on Nvidia.
|
|
|
|
Any updates coming for this miner?
There is no faster miner already so what's the point to update it?  |
|
|
|
With 110GB Virtual Memory last version is not working on rigs 4x 1080ti 2x 1070ti with default settings, it's disabling few gpus all the time  |
|
|
|
New version 2.1.18 ready for download.
Release notes:
- New option: -log creates a logfile that contains the screen output and
additional information that could be helpful to find bugs.
- New option: -luck shows a second statistic line - additional to the rig
speed. It shows the time it may take to find a new solution(share)
at the current difficulty. It also calculates a 'luck' value that
show the luck in percent for the next share.
- New option: --api-type does nothing so far, TT-Miner support TCP connections only
- Remove the three stars in the 'Accepted share' message.
- The meaning of the -A parameter changed slightly. If you define an algo without
- cuda version, TT-Miner will load the algo that fits best to your installed
- driver version - it will no longer load the algo for the last cuda version!
Please report all issues and bugs you find.
Thanks.
This version does not work for me on any rig, it turns off without any message after "work received". |
|
|
|
it's also luck but i compared whattomine 24 hour profit for that day and mintpond showed much better results at least for one day, actually difficulty was little bit higher when i tested mintpond
Just switched my 160mh/s to mintpond, last month it was on 2miners, im going to compare it after few days  |
|
|
|
for my rig mintpond was clear winner with hashrate of 14.3mh.sec TDP 70% + intensity 21 with 2miners i got only 0.475 zcoins (whattomine calculator showed 0.55) vs 0.60 zcoins on mintpond (whattomine calculator showed 0.545 zcoin) today i will test intensity 22 on mintpond european server for 24 hours, then default intensity 20 as well let's see which is more profitable, with intesnity 21 stability was fine, i think 22 intensity is too much for my rig (some slowdowns and rejected shares), then i will test with intensity 20 and find out which give better average hashrates 20 or 21, with intensity 20 hashrate is same as with intensity 21, intensity 22 had 15mh/sec, while intensity 20-21 both have 14.3mh/sec in miner
It's impossible to compare day by day. One day diff is a bit higher another day a bit lower. |
|
|
|
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 |
|
|
|
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 |
|
|
|
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.zipThanks 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 |
|
|
|
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.zipThanks and happy mining. Not enyough memory to run the algo, many rigs with this error on 2.1.16, previous version everything fine |
|
|
|
Hello Any plans to add Zilminer for dual mining? |
|
|
|
|
ayone managed to configure it with awsome miner?
|
|
|
|
nothing is profitable yet and it seems tides will be turning soon.
Hehe you expect next gold rush soon? |
|
|
|
requires 7.4GB VRam, will work on 8GB cards under Linux and Windows 7
Works on Windows 8... Windows 8 support 12 GPUs? |
|
|
|
|
50mh per rx 580 4gb nitro+ lyra2rev3
|
|
|
|
this version is a complete bust for me for all my nvidia cards for nicehash for windows 10. Version 1.24 worked for my 1080ti/1070 for nicehash somewhat, However, version 1.25 i get:
connect to beam.usa.nicehash.com:3370 Failed: stream truncated
I get this error for all 1080ti/1070/1060 on four different systems with windows10 using 1.25. i get zero hashrates. this is for beam.. i.e. equihash150
zhash, i.e. equihash144 works fine on nicehash.
Would be great if developers would stop support this nicehash cancer. Zminer consider this. Regards |
|
|
|
II would not advise buying products from Zotac and Gainward. They have very poor cooling system. It is not good for mining.
I would recomend you Zotac becouse they have 5y warranty, who cares about quality if you can have new card every year RMAing it? |
|
|
|
on BEAM my 570s 4GB and 470s 4GB went from about 10.8 down to 8 on alpha 3 compared to alpha 2.
One of my rigs is not starting with newest version. It's failing on initializing gpus. |
|
|
|
|
