Hi miniZ,
Thank you so much for the continued efforts to improve mining Beam. W
What version of Nvidia drivers is your team testing on?
Also, do you have a SHA256 checksum for the latest testing version?
Thanks!
Topic: miniZ v2.0a Equihash 144,5 125,4 210,9 150,5 192,7 BeamHash3 ProgPoW Ethash CFX - page 57. (Read 59767 times)
April 28, 2019, 03:26:03 PM
April 28, 2019, 01:35:31 PM
FYI, v1.3n++ still have the same 'losing miner' on pool. Cheers.
Hi ARTRN, Thanks a lot for your quick feedback.
It looks like you can replicate faster the problem than we do!
Now, we know what it is (the communication with the pool gets into some weird state and the miner
was getting stuck trying to recover). We fixed it, but it still requires testing...
This stage will be much faster with some extra help
The miniZ v1.3n++ testing version (Win 10, Cuda10) was updated. You can download from our Download page https://miniz.ch/download/
We did not change the version name, so check you have the right build with miniZ.exe --version
It should be Apr 28 2019 12:28:20
Cheers,
miniZ
Hi, miniZ v1.3n++ testing version (Win 10, Cuda10) Apr 28 2019 12:28:20 so far so good.
It's been running close to 4 hours without fail.
Cheers.
miniZ - I agree. I am at 5 hours now with no issues, so I am hopeful. CPU utilization is holding steady so far. I need to get to 12 hours with no issues before I will be pretty confident that it is resolved.
April 28, 2019, 01:14:24 PM
FYI, v1.3n++ still have the same 'losing miner' on pool. Cheers.
Hi ARTRN, Thanks a lot for your quick feedback.
It looks like you can replicate faster the problem than we do!
Now, we know what it is (the communication with the pool gets into some weird state and the miner
was getting stuck trying to recover). We fixed it, but it still requires testing...
This stage will be much faster with some extra help
The miniZ v1.3n++ testing version (Win 10, Cuda10) was updated. You can download from our Download page https://miniz.ch/download/
We did not change the version name, so check you have the right build with miniZ.exe --version
It should be Apr 28 2019 12:28:20
Cheers,
miniZ
Hi, miniZ v1.3n++ testing version (Win 10, Cuda10) Apr 28 2019 12:28:20 so far so good.
It's been running close to 4 hours without fail.
Cheers.
April 28, 2019, 11:44:18 AM
https://i.imgur.com/OMGwSrh.png
v1.3n+ and v1.3n++ (beta build, Apr 28 2019 12:28:20) CUDA 10 versions doesn't work on sparkpool, see picture above.
Sparkpool is displaying that there are too many rejected shares, but it's not reporting it back to miner, so in miner it looks good, but on poolside >95% of shares are rejected (or stales).
Then I left it to mine on leafpool and it keeps mining fine for more than 8 hours.
Only thing I noticed is that at some point it hits 100% CPU usage and stays like that, I need to investigate this more.
CPU: Celeron G3930 (@2.90 GHzm 2C/2T)
RAM: 4 GB
Virtual Mem.: 64 GB
GPUs: 1x 1080ti MSI Gaming
5x 1080 inno3d twin X2
OS: Windows Server 2016 (version 1607, OS Build 14393.2273)
Nvidia driver: 419.17 (CUDA 10.10)
MSI Afterburner (for OC): 4.6.0 -> noting this as it can be cause of 100% CPU usage, because on 1080ti fanspeed readings in miniZ console becomes 0%, maybe there are conflict between querying Nvidia-SMI stats from miner and Afterburner, idk.
v1.3n+ and v1.3n++ (beta build, Apr 28 2019 12:28:20) CUDA 10 versions doesn't work on sparkpool, see picture above.
Sparkpool is displaying that there are too many rejected shares, but it's not reporting it back to miner, so in miner it looks good, but on poolside >95% of shares are rejected (or stales).
Then I left it to mine on leafpool and it keeps mining fine for more than 8 hours.
Only thing I noticed is that at some point it hits 100% CPU usage and stays like that, I need to investigate this more.
CPU: Celeron G3930 (@2.90 GHzm 2C/2T)
RAM: 4 GB
Virtual Mem.: 64 GB
GPUs: 1x 1080ti MSI Gaming
5x 1080 inno3d twin X2
OS: Windows Server 2016 (version 1607, OS Build 14393.2273)
Nvidia driver: 419.17 (CUDA 10.10)
MSI Afterburner (for OC): 4.6.0 -> noting this as it can be cause of 100% CPU usage, because on 1080ti fanspeed readings in miniZ console becomes 0%, maybe there are conflict between querying Nvidia-SMI stats from miner and Afterburner, idk.
April 28, 2019, 10:23:25 AM
With 1.3n+ I also have a problem that my worker just disappear from the pool but it keeps hashing on my rig. I will try 1.3++ now.
Also on Windows 10, 6x GTX1060 6GB and a G3930 CPU with version 1.3n+ is still 100% CPU usage.
EDIT: With 1.3++ my LA on Hive OS rig is 5,6+ again.
Hi MineOrDie,Also on Windows 10, 6x GTX1060 6GB and a G3930 CPU with version 1.3n+ is still 100% CPU usage.
EDIT: With 1.3++ my LA on Hive OS rig is 5,6+ again.
Thanks for keeping us posted.
We did not update the Hive OS package yet.
We are currently testing and looking into it. (we think we got the offline issue already)
Cheers
April 28, 2019, 09:44:16 AM
I and 2 of my mining buddies can confirm the 1.3n+ did not resolve the "OFFLINE WORKER" issue as it is still happening. I really hope you guys get to the bottom of that issue soon. Thanks
Just fired up the new version now. Ill let you know how it goes. it was consistently failing every 6-10 hours. If you don't mind me asking what did you find going on?
Hi sharmanov, BIOLERUP4LIFE,
Thanks for all the feedback.
We think we got it now, sometimes (not often) the communication with the pool gets into some weird state and the miner
was getting stuck in a loop trying to recover. We fixed it, but it still requires testing...
For now, we made available a miniZ v1.3n++ testing version (Win 10, Cuda10).
You can download from our Download page https://miniz.ch/download/
To check if you have the right build run miniZ.exe --version
It should be Apr 28 2019 12:28:20
Thanks again.
Cheers
April 28, 2019, 09:33:59 AM
FYI, v1.3n++ still have the same 'losing miner' on pool. Cheers.
Hi ARTRN, Thanks a lot for your quick feedback.
It looks like you can replicate faster the problem than we do!
Now, we know what it is (the communication with the pool gets into some weird state and the miner
was getting stuck trying to recover). We fixed it, but it still requires testing...
This stage will be much faster with some extra help
The miniZ v1.3n++ testing version (Win 10, Cuda10) was updated. You can download from our Download page https://miniz.ch/download/
We did not change the version name, so check you have the right build with miniZ.exe --version
It should be Apr 28 2019 12:28:20
Cheers,
miniZ
April 28, 2019, 09:25:36 AM
Hi everyone,
Again, tanks a lot for your feedback!
There is a new miniZ version v1.3n+ for you to download.
* Reduced CPU usage to background levels.
* Better invalid share detection.
* Ignore pers auto for 150,5.
* Fixing issues with worker going offline.
Again, tanks a lot for your feedback!
There is a new miniZ version v1.3n+ for you to download.
* Reduced CPU usage to background levels.
* Better invalid share detection.
* Ignore pers auto for 150,5.
* Fixing issues with worker going offline.
I and 2 of my mining buddies can confirm the 1.3n+ did not resolve the "OFFLINE WORKER" issue as it is still happening. I really hope you guys get to the bottom of that issue soon. Thanks
April 28, 2019, 08:34:42 AM
The miniZ v1.3n++ testing version (Win 10, Cuda10) was updated. You can download from our Download page https://miniz.ch/download/
We did not change the version name, so check you have the right build with miniZ.exe --version
It should be Apr 28 2019 12:28:20
Cheers,
miniZ
We did not change the version name, so check you have the right build with miniZ.exe --version
It should be Apr 28 2019 12:28:20
Cheers,
miniZ
miniZ - I have this latest version running on my 3 rigs right now. The CPU utilization is a little better on my two Celeron rigs (74% and 89% instead of 100%). I'll let you know how it goes.
April 28, 2019, 08:28:24 AM
MiniZ is faster on my 1070s vs Gminer; however Gminer is faster on my 1080ti.
I noticed f11=1 (stock setting I think) is the best one with oc2. I’ve teied “2” and “3”3 and “0” for f11 values and it’s slower on these other values
Hi impynick,I noticed f11=1 (stock setting I think) is the best one with oc2. I’ve teied “2” and “3”3 and “0” for f11 values and it’s slower on these other values
Thanks for reporting this.
Could you share your hashrate and OC values for those GPUs?
Cheers
April 28, 2019, 08:25:50 AM
With 1.3n+ I also have a problem that my worker just disappear from the pool but it keeps hashing on my rig. I will try 1.3++ now.
Also on Windows 10, 6x GTX1060 6GB and a G3930 CPU with version 1.3n+ is still 100% CPU usage.
EDIT: With 1.3++ my LA on Hive OS rig is 5,6+ again.
Hi MineOrDie,Also on Windows 10, 6x GTX1060 6GB and a G3930 CPU with version 1.3n+ is still 100% CPU usage.
EDIT: With 1.3++ my LA on Hive OS rig is 5,6+ again.
Thanks for keeping us posted.
We did not update the Hive OS package yet.
We are currently testing and looking into it. (we think we got the offline issue already)
Cheers
April 28, 2019, 08:20:16 AM
no worries thanks for the response on it. it was the only thing i could think of but if it had been the case then it would have stuck on the 4minute initiation of the devfee, not after 5 hrs . good luck finding the issue.
Thanks a lot for the tips, they are much appreciated.
We think we got this one. Testing it still.
Cheers
April 28, 2019, 08:15:29 AM
FYI, v1.3n++ still have the same 'losing miner' on pool. Cheers.
Hi ARTRN, Thanks a lot for your quick feedback.
It looks like you can replicate faster the problem than we do!
Now, we know what it is (the communication with the pool gets into some weird state and the miner
was getting stuck trying to recover). We fixed it, but it still requires testing...
This stage will be much faster with some extra help
The miniZ v1.3n++ testing version (Win 10, Cuda10) was updated. You can download from our Download page https://miniz.ch/download/
We did not change the version name, so check you have the right build with miniZ.exe --version
It should be Apr 28 2019 12:28:20
Cheers,
miniZ
April 28, 2019, 06:51:34 AM
FYI, v1.3n++ still have the same 'losing miner' on pool. Cheers.
April 28, 2019, 05:45:05 AM
MiniZ is faster on my 1070s vs Gminer; however Gminer is faster on my 1080ti.
I noticed f11=1 (stock setting I think) is the best one with oc2. I’ve teied “2” and “3”3 and “0” for f11 values and it’s slower on these other values
I noticed f11=1 (stock setting I think) is the best one with oc2. I’ve teied “2” and “3”3 and “0” for f11 values and it’s slower on these other values
April 28, 2019, 04:02:46 AM
With 1.3n+ I also have a problem that my worker just disappear from the pool but it keeps hashing on my rig. I will try 1.3++ now.
Also on Windows 10, 6x GTX1060 6GB and a G3930 CPU with version 1.3n+ is still 100% CPU usage.
EDIT: With 1.3++ my LA on Hive OS rig is 5,6+ again.
Also on Windows 10, 6x GTX1060 6GB and a G3930 CPU with version 1.3n+ is still 100% CPU usage.
EDIT: With 1.3++ my LA on Hive OS rig is 5,6+ again.
April 28, 2019, 01:42:28 AM
1. Ok done it. As far as I know, Hive guys already added miniZ to their miners repo and I was told they'll make it public next week.
2. It happens every run. HiveOS, 418.43 drivers, beam 150,5 on the nicehash. The rest of miners I use (gminer/t-rex/ethminer) giving me LA 2-3, tops. Log and LA as follows:
At the top of the top (pun intended) are miniZ and kworker.
Thanks for the info! It is good to know 2. It happens every run. HiveOS, 418.43 drivers, beam 150,5 on the nicehash. The rest of miners I use (gminer/t-rex/ethminer) giving me LA 2-3, tops. Log and LA as follows:
At the top of the top (pun intended) are miniZ and kworker.
This has been fixed in the new miniZ version v1.3n+.
You will need to update your flightsheet: https://miniz.ch/2019/04/26/hive-os-support-6/
Please check it out and let us know how it goes.
Yay! LA is good now.
April 27, 2019, 09:22:31 PM
Im also having the same issue as above where the miner is mining locally but shows offline in the pool while mining beam on sunpool.top. Ill try and help any way that i can just let me know how
I doubt it's the pool. Mining on pool.btc.com. It happened randomly.
Cheers.
Hi BIOLERUP4LIFE, ARTRN,Cheers.
Thanks. Yes it does not seem to be pool related.
Did you notice an increase in cpu load when it happened?
Cheers
It does not seem to be related. This was one of the first things we checked.
It seems to be related whith some changes we introduced with the new algo.
We keep digging.
Thanks.
Cheers
no worries thanks for the response on it. it was the only thing i could think of but if it had been the case then it would have stuck on the 4minute initiation of the devfee, not after 5 hrs . good luck finding the issue.
April 27, 2019, 09:04:58 PM
Latest 1.3n+ still suffer from miner offline in pool just like the previous version. Whatever changes on this version doesn't fix the dreaded offline. Mining on algo 150.5.
Hi ARTRN,We are sorry about that...
We really want to get rid of that issue, but it is very hard to replicate.
On which pool were you mining?
Thanks.
Cheers
Which OS are you using? And NVIDIA driver?
We made a few modifications and can compile a version for testing. Since you offered your help
Thanks.
Cheers
Hi BIOLERUP4LIFE,
You can download a testing version (win10, Cuda 10) v1.3n++ here.
Let us know if the problem persists with this one.
Thanks a lot!
Cheers
April 27, 2019, 08:12:53 PM
Latest 1.3n+ still suffer from miner offline in pool just like the previous version. Whatever changes on this version doesn't fix the dreaded offline. Mining on algo 150.5.
Hi ARTRN,We are sorry about that...
We really want to get rid of that issue, but it is very hard to replicate.
On which pool were you mining?
Thanks.
Cheers
Which OS are you using? And NVIDIA driver?
We made a few modifications and can compile a version for testing. Since you offered your help
Thanks.
Cheers
Jump to: