Topic: TT-Miner 2022.4.1 KAWPOW, PROGPOW, ETHASH, ETCHASH, EPIC, SHA512256D, GHOSTRIDER - page 40. (Read 132259 times)
April 13, 2019, 10:08:39 AM
because PM works once in a day have to write answer here: looks like beta2-version fixed connections bug for me. But miner doesn't pausing process while no connect.
April 12, 2019, 05:52:55 AM
2.2.2 beta2 hang up first cards on all my rigs after near half hour working on MTP - only that cards on each rig which connected to pci x16 , another cards connected to pci x4 working normally
Hi. That sounds strange. Could you please run the miner with -log and -logpool and DM me the log files please?
Thanks.
April 12, 2019, 05:15:49 AM
2.2.2 beta2 hang up first cards on all my rigs after near half hour working on MTP - only that cards on each rig which connected to pci x16 , another cards connected to pci x4 working normally
April 11, 2019, 09:18:12 AM
Hey there I have hashrate issues when using MTP on Win7 even with the correct Cuda vs driver per instructions. I have tried it many different ways , uninstall reinstall several different machines in the farm. Is this just a Win7 thing? The Win10 machines seems fine for the most part. Any recommendations? The hashrate for 1080ti is abou 2MH I can play with clocks and get them a little higher, but would love to get this to work on all my machines, thanks and great job already 
Hi,
yes I heard about the Win7 performance lack. If my memory serves me right this is an issue that all miners for MTP shows - but I'm not sure about that? I think it is a Windows 7 issue. Maybe you can give a different miner a try and let me know iof it works well performance wise on your system. I will then check if I find some Windows 7 relates issues.
So please let me know.
Thanks for reporting.
P.S. Nice profile picture!
Windows ...
It seems it has issues with MANY algos, on MANY miners for all sorts of reasons. The memory management in Windows 10 has been improved greatly over Windows 7 (though no where near the level that Linux is currently) which is one of the main improvements over Windows 7.
So chances are it isn't 'really' anything to do with your systems bar the OS you are using.
#crysx
Thanks for the replies gents I figured as much it being Win7 related. And yes I have tried the other miners and same results. So it's a matter of , do I want to upgrade them to Win10 ( a lot of machines ) or do I go with a Linux based mining OS ...ughhh either way will be a pain since I have used awesomeminer for quite some time for management. YEah the profile pic , LOL right!
I think what I will do is convert 1 machine to Win10 and confirm a fix just to know and report here. As far as performance with other algos I have not ran across any other than MTP with lower performance on Win7 vs 10 but I imagine it is inevitable that I would eventually, let you know
April 11, 2019, 07:32:55 AM
Hey there I have hashrate issues when using MTP on Win7 even with the correct Cuda vs driver per instructions. I have tried it many different ways , uninstall reinstall several different machines in the farm. Is this just a Win7 thing? The Win10 machines seems fine for the most part. Any recommendations? The hashrate for 1080ti is abou 2MH I can play with clocks and get them a little higher, but would love to get this to work on all my machines, thanks and great job already
Hi,
yes I heard about the Win7 performance lack. If my memory serves me right this is an issue that all miners for MTP shows - but I'm not sure about that? I think it is a Windows 7 issue. Maybe you can give a different miner a try and let me know iof it works well performance wise on your system. I will then check if I find some Windows 7 relates issues.
So please let me know.
Thanks for reporting.
P.S. Nice profile picture!
Windows ...
It seems it has issues with MANY algos, on MANY miners for all sorts of reasons. The memory management in Windows 10 has been improved greatly over Windows 7 (though no where near the level that Linux is currently) which is one of the main improvements over Windows 7.
So chances are it isn't 'really' anything to do with your systems bar the OS you are using.
#crysx
April 10, 2019, 10:37:33 PM
Hey there I have hashrate issues when using MTP on Win7 even with the correct Cuda vs driver per instructions. I have tried it many different ways , uninstall reinstall several different machines in the farm. Is this just a Win7 thing? The Win10 machines seems fine for the most part. Any recommendations? The hashrate for 1080ti is abou 2MH I can play with clocks and get them a little higher, but would love to get this to work on all my machines, thanks and great job already
Hi,
yes I heard about the Win7 performance lack. If my memory serves me right this is an issue that all miners for MTP shows - but I'm not sure about that? I think it is a Windows 7 issue. Maybe you can give a different miner a try and let me know iof it works well performance wise on your system. I will then check if I find some Windows 7 relates issues.
So please let me know.
Thanks for reporting.
P.S. Nice profile picture!
April 10, 2019, 10:34:02 PM
i'm testing TT-Miner-2.2.2-beta2 and see some gridsize changes with default intensity, now it starts from lower gridsize and increasing little by little, also there's blocksize as well:
https://i.imgur.com/Fxs75ac.png
https://i.imgur.com/Fxs75ac.png
Hi
- yes, this is one of the new function for the new release that comes with some fixes for re connection. If you do not specify a value for intensity and grid size TT-Miner will try to find the best setting. Depending on the algo this process may take up to 60 minutes. The miner have to wait for stable hash rates first before it can continue with the next value set. Let me know if that works for you.
April 10, 2019, 08:41:18 PM
Hey there I have hashrate issues when using MTP on Win7 even with the correct Cuda vs driver per instructions. I have tried it many different ways , uninstall reinstall several different machines in the farm. Is this just a Win7 thing? The Win10 machines seems fine for the most part. Any recommendations? The hashrate for 1080ti is abou 2MH I can play with clocks and get them a little higher, but would love to get this to work on all my machines, thanks and great job already
April 10, 2019, 05:50:34 PM
i'm testing TT-Miner-2.2.2-beta2 and see some gridsize changes with default intensity, now it starts from lower gridsize and increasing little by little, also there's blocksize as well:
https://i.imgur.com/Fxs75ac.png
https://i.imgur.com/Fxs75ac.png
April 08, 2019, 05:31:58 PM
I noticed that miner doesn't stop mining threads when connection to pool stratum is lost, it's tries to reconnect but until then mining is not not suspended.
This is ok when disconnects are short, but when they are longer this is bad.
Pls. implement this behavior, it would be nice to have config param to specify disconnect timeouts, and then to stop mining even exit the miner.
Thx. I started testing this miner on MTP, and I'm still looking for optimal intensity and grid size for 1080 and 1080ti.
For now I like it's stability and constant GPU/POWER usage.
This is ok when disconnects are short, but when they are longer this is bad.
Pls. implement this behavior, it would be nice to have config param to specify disconnect timeouts, and then to stop mining even exit the miner.
Thx. I started testing this miner on MTP, and I'm still looking for optimal intensity and grid size for 1080 and 1080ti.
For now I like it's stability and constant GPU/POWER usage.
Hi,
thanks for your report.- I'm working on this issue already. You can specify a backup/fail-over pool until I found the bug and release a fix. Finding the sweet-spot for gridsize is somewhat tricky since all high values are very close together. I made the experience that from a certain value for gs the hash-rates starts high, but continue to drop the shortly after.
Thanks for your support.
Hi I specified failover pool, that's working fine.
But I mean that when Internet connection is cut to rig, like when ISP went down, or when you unplug LAN cable from rig (to simulate loss of connectivity).
Miner just show that connection to stratum is lost and whole time Power Consumption/GPU Usage is same like mining regulary, but now is wasting power.
I wouldn't notice this flaw if my ISP didn't started having problems recent days, but they fixed their network infrastructure after few days.
April 08, 2019, 08:46:25 AM
i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.
Hi, did you try -b 127.0.0:4068 or --api-bind 127.0.0:4068? This should enable the API for miner-monitoring - and as far as I know it works with some of the monitoring software out there. Which software do you use?
I use eth monitoring. I had been trying to use --api-bind 0.0.0.0:4068 since that usually works for most miners but it returns an error and the miner won't start with yours. 127.0.0.0:4068 runs without issue but is not recognized by eth monitoring.
Hi- sorry, my bad. it should read 127.0.0.1 for localhost. Let me know if that works. I can add 0.0.0.0 to be localhost for a future release.
I'm going to switch all my rigs over today, thanks for the help. April 08, 2019, 07:57:47 AM
i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.
Hi, did you try -b 127.0.0:4068 or --api-bind 127.0.0:4068? This should enable the API for miner-monitoring - and as far as I know it works with some of the monitoring software out there. Which software do you use?
I use eth monitoring. I had been trying to use --api-bind 0.0.0.0:4068 since that usually works for most miners but it returns an error and the miner won't start with yours. 127.0.0.0:4068 runs without issue but is not recognized by eth monitoring.
Hi- sorry, my bad. it should read 127.0.0.1 for localhost. Let me know if that works. I can add 0.0.0.0 to be localhost for a future release.
April 08, 2019, 07:13:29 AM
i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.
Hi, did you try -b 127.0.0:4068 or --api-bind 127.0.0:4068? This should enable the API for miner-monitoring - and as far as I know it works with some of the monitoring software out there. Which software do you use?
I use eth monitoring. I had been trying to use --api-bind 0.0.0.0:4068 since that usually works for most miners but it returns an error and the miner won't start with yours. 127.0.0.0:4068 runs without issue but is not recognized by eth monitoring.
April 08, 2019, 05:38:59 AM
i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.
Hi, did you try -b 127.0.0:4068 or --api-bind 127.0.0:4068? This should enable the API for miner-monitoring - and as far as I know it works with some of the monitoring software out there. Which software do you use?
April 08, 2019, 05:34:26 AM
i would really like to use this miner but there is no way that i can until api access is enabled. I need it for remote monitoring of rigs. Please enable this feature in a future release.
April 08, 2019, 03:58:47 AM
I noticed that miner doesn't stop mining threads when connection to pool stratum is lost, it's tries to reconnect but until then mining is not not suspended.
This is ok when disconnects are short, but when they are longer this is bad.
Pls. implement this behavior, it would be nice to have config param to specify disconnect timeouts, and then to stop mining even exit the miner.
Thx. I started testing this miner on MTP, and I'm still looking for optimal intensity and grid size for 1080 and 1080ti.
For now I like it's stability and constant GPU/POWER usage.
This is ok when disconnects are short, but when they are longer this is bad.
Pls. implement this behavior, it would be nice to have config param to specify disconnect timeouts, and then to stop mining even exit the miner.
Thx. I started testing this miner on MTP, and I'm still looking for optimal intensity and grid size for 1080 and 1080ti.
For now I like it's stability and constant GPU/POWER usage.
Hi,
thanks for your report.- I'm working on this issue already. You can specify a backup/fail-over pool until I found the bug and release a fix. Finding the sweet-spot for gridsize is somewhat tricky since all high values are very close together. I made the experience that from a certain value for gs the hash-rates starts high, but continue to drop the shortly after.
Thanks for your support.
April 04, 2019, 05:40:09 AM
Hi,
please run this beta with the command line option -logpool and -log. I have added some more debug information that might help me to find out what's going on on your system. I tried a lot, but I could not reproduce it here on my Win10 systems.
https://TradeProject.de/download/Miner/TT-Miner-2.2.2-beta1.zip
If you see the bug, please stop the miner and send me the logfiles.
Thanks for your support.
April 04, 2019, 05:39:41 AM
Hey Trailing,
on MTP your miner atm is the fastest on GTX cards, but have some problems on mixed rigs with 1070/1080 cards, dunno why.
But on RTX cards your miner is much slower than your competitor. Are there any more improvements possible?
on MTP your miner atm is the fastest on GTX cards, but have some problems on mixed rigs with 1070/1080 cards, dunno why.
But on RTX cards your miner is much slower than your competitor. Are there any more improvements possible?
Hi,
did you try to 'play' around with intensity or grid size. You can set these values for each gpu separate. Please try this for the RTX as well - if you haven't tried it yet. Unfortunately I do not have a RTX available and cannot run my own test, but maybe someone from the community can help - or give me some more information what the problem could be???
Thanks.
>>>You can set these values for each gpu separate
Either but not both, this case will not work: -d 0,1,2 -i 15,16,17
You can't have both -d & -i at the command line. Can you fix that?
Hi, is the bug fixed in the version I sent you?
Please let me know.
Thanks
April 03, 2019, 07:26:13 PM
Does it work again if you restart the miner?
yes, but is tired to check almost every single moment since the miner is not stable.
April 03, 2019, 03:56:50 AM
i understand, thing is my rig has higher average hashrates on mintpond using older 2.1.19 build with intesnity 20 and gridsize 4096 on all 5 GPU, with later builds it has intensity 15 and grid sizes are 7000+ for GTX1080Ti and 5000+ for GTX1080 but i don's see any hashrates improvements in 24 hour period, difference is around 1mh/sec daily average 16mh.sec+ VS 15mh.sec on newer builds, so maybe better to use older build at the moment with lower default gridsize, miner hashrates itself are more or less same with both builds
That's correct, older version reports better hashrate on poolside, it's about 3-4% in my case. Jump to: