Topic: Hash Auger 2.9.7.5 Mining Manager and Switcher for NVIDIA GPUs - page 25. (Read 8798 times)

Thank you that really made things easier to keep track off.

Let me know if you notice any other issues with the developer contribution. I'll try to do some more testing of alternative scenarios to see if there are any other cases where it may not work as intended. Thanks for the TeamViewer info; perhaps the problem only occurs when there isn't a monitor plugged into the rig at all. You are correct about Klaust; the config file is currently grabbing the Cuda 8 version instead of the Cuda 9.1 version. Sorry I missed that last night. I'm already testing the software with the other version of the miner and it seems to be a seamless replacement. NiceHash just changed how a couple of their algorithms are priced, so I need to send out a small update today anyways.

Certainly understandable on all accounts.  I don't have an issue with the 20 mins as long as it's done once, regardless of how many times I may have had to reboot that day (for whatever reason) or via freezes.  I know it wasn't your intention to have it do that, but as I've noticed it quite a few times (letting it go all the other times); last night was the kicker when I wanted to try to install more RAM to (maybe) fix the freezing issue, and couldn't risk restarting HA without (maybe) another developer contribution kicking in (or not).

No need to divide the time into smaller chunks if the 20 min block works as intended, in my opinion.  I was only suggesting in the event there was no good way to fix the issue, then in my last night example and I had 1 hour left of mining in the "day" before midnight, then I would have only risked a 5 min contribution and not a 20 min one (after I had done 40 mins for sure earlier that day).

Thank you for addressing.

Nice! Thanks for addressing. 

(1) Yeah I would imagine it would be hard to make sure the developer contribution was recorded if there was a crash or something (which is in case what happens with me on occasion).  Maybe writing it to the log files as soon as the contribution is done for the day (or something)?  I'm not a coder in any way so I'm not sure how you actually do it now.

On Teamviewer, I haven't really had issues others are saying. HA shows up fine (i.e. not a blank window). Any team viewer issues I've had have been on connection to the program itself, having nothing to do with HA.  Note, my monitor is plugged into my motherboard and NOT any of the cards I use for mining.

(2) Nah no worries, was just curious.  Not necessary.

(3) There's no particular pattern that I can see. The last time I caught it, it was lyra2v2....but that algo runs fine other times. Agree on xevan, that one is cuda 8, but I caught another one (randomly) this morning while it was mining skein on klaust (I think)?

(4) Also no worries here on notifications; I can imagine the privacy concerns and this being easier said than done.  Certainly not a priority.  Would rather you focus your efforts as you are re: expanding functionality, addressing user concerns, etc.

Thanks!

Adding the Pool and Coin information to the Klaust miner panels was a simple change, so I was able to include it in 1.7.1 after all.  Thanks for the feedback.

I did track down an issue where the developer contribution could run a second time in the same day if the system was rebooted after the first developer contribution ran.  The exact circumstances were a little more complicated than just restarting the computer, but obviously any extra developer contribution is one too many. Thank you for bringing it to my attention and please accept my sincere apologies; I try to be as transparent and fair as possible with the contributions, so any bugs with the process are my highest priority. I understand the intent of your suggestion to divide the time into smaller chunks. I'm willing to consider making that change if the twenty minute block continues to have issues. My concerns are mainly based on how smaller chunks of time would cause a increase in lost productivity for users due to the extra task switching and that adding complexity to the process could make it more error-prone. As I said though, I want the process to be fair for everyone, so I am open to the idea that a single block may not be ideal.

I already have Miningspeedpool on my list to look at. I wasn't aware that Zpool had a dedicated pool, if you could post a link, I'll take a look at it too. Sorry to hear you are having issues reading the font.  Is the font size too small or do you have a different issue? Is it in a particular spot or throughout the entire application?  The more specifics that I know, the faster I can try to resolve the issue.

There is something going on with keccak that is driving a lot of traffic to that pool. Remember how yesterday I said the hash rate doubled a couple of times to 80,000 gh/s? Well, today it spiked to over 200,000 gh/s and the price at one point today was close to .3mBTC/GH/Day, which is higher than it was yesterday. I don't know how accurate the pool's price estimates are for that algorithm, but evidently a lot of different miners think they are legit. As for x17, the price keeps fluctuating betwen .02 and .04 mBTC/MH/Day according to the Zpool website, so $4 seems possible for a 1070ti a the high end of that. Verge just came back after the recent attack, so its pricing is pretty volatile right now.

My advice has always been to find a few pools that you like and just mine on them. If you doubt a pool's estimates, you can always disable the pool for awhile and come back to it later to see if the estimates have gotten any better .  

I'ved heard positive things Mining speed pool and of zpools dedicated pool. Can we get font that is clear on the next version please/

Zpool has been the most incorrect for me. It still shows me in the $6 range for keccak cpu mining, and $4 on a 1070 ti for x17(seems high for the current market, but then again maybe the algo hit?).

That feature is coming in handy for a lot of different reasons lately. Is that on Zergpool or a different pool? I haven't seen x13 priced like that on my rigs and I verified that the price estimate should be based on MH/s on that pool.  What's your benchmarked hash rate for that algorithm?

whats up with x13 the last few days?   It has been reported to be paying between $23 and $356.   I know this is an error but where does the error come from?   Luckily I have the auto price set to rule out these kind of errors.

That is definitely not the intended behavior. The software should keep track of whether or not the dev fee has run for the day regardless of the number of times you stop and then restart it. An exception would be if you delete the .exe file or if the dev contribution is interrupted by the user or a system crash. I'll run some tests on my machines to see if stopping/restarting the software is causing the developer contribution to run more often than it should before I release 1.7.1 so I have an opportunity to fix it as soon as possible.

Since you mentioned TeamViewer, I have to ask if you had to change any settings to get Hash Auger to display properly. Some users are reporting that the software is just a blank window in TeamViewer but the problem goes away when they hook up a monitor to the rig.


It is possible to update the miners by editing the config files. However, if the mining software changes its screen output format, the software may not be able to parse it correctly which would probably result in some broken functionality. Also, if the miner adds algorithms, there would be other config changes that would also need to be made.  However, I could probably type up some directions for advanced users such as yourself.

Speaking of Nevermore, 1.7.1 will include the new merged version of Nevermore so x16s should be a little faster.



Looking at the miner output, Xevan appears to be the only variant of CCminer that still uses Cuda8. Unfortunately, that miner has never been updated, so I don't expect that to change. You can try disabling that algorithm and see if it helps your stability issues. Is there a pattern to which algorithm(s) the software is mining when the system freezes?



I definitely appreciate the feedback, especially about the developer contribution - that is something I want to address as quickly as possible.  I'm definitely thinking about including support for offline notifications, I just need to setup a cloud repository for that functionality since the feature wouldn't work too well if the contact information was stored on the rig and the rig was down. Unfortunately, that means working out some security and privacy concerns before I can put it into place.

I can see where that would be useful. I'm not sure if it will be in 1.7.1, but I will definitely make the change for 1.8. In the meantime, that information should already be visible in the the Output box at the bottom of the Mine tab.  FYI, MiningPoolHub changed something in their API last night or earlier today that broke Cryptonight in Hash Auger and a few other programs.  I'm testing a fix now, which is why I can't guarantee that the change to the miner stat panels for Klaust will be in 1.7.1.

A few discussion points:

(1) Is it in the eventual plan to change up how the developer contribution works? Not necessarily the amount of fee, but how it's obtained. While I love your software, it is a bit unorthodox in terms of the one 20 min block of time. Normally I wouldn't care about the one block, but here's why it matters for me.

Every day without fail my computer will freeze for some odd reason. I am not necessarily blaming HA...it could be it but I can't prove it for sure (it could also be Teamviewer screwing with me).  Sometimes I'll find the machine frozen and others it'll just have basically restarted back to square one.  Every time it does that, assuming I restart HA, I "reset" the developer contribution.  As discussed with you before, the software is designed to get that contribution no matter how many minutes left in the day there is (generally).  If there is 1 hour left in the day and you're just starting your mining for the day (or you've just rebooted your computer), it's going to donate another 20 mins no matter how many times you've already donated that day.

Today is a prime example of this. I've done (at a minimum) two 20 minute donations today.  Once during the morning before my 3pm freeze/reset, and once after I rebooted (that's all I'm aware of, I haven't checked logs to see if there are other reboots in there). I actually ordered another 16 GB of RAM for my rig to see if it might help the freezing..it seems to occur upon coin switch (i.e. the "starting" of 8 different ccminer processes).  I figured more RAM above and beyond my 8 GB existing would help.  I want to install that right now, but if I do and restart HA, I'll donate ANOTHER 20 mins to you in the ~1 hour left before midnight.   Maybe the RAM will solve my issues here and this won't be a problem anymore, but in general this doesn't seem like the ideal way to go about this.

Is there any consideration with modifying the formula to be shorter blocks (e.g. 5 mins every 6 hours of mining), or maybe a way to track on your end that we've made the required contribution for the day so that if I have to reboot, I won't be held hostage?

(2)  Separate request or question - is it possible to manually update miners without waiting for you to update HA? For example (making up versions), if the current version of HA had nevermore 2.2 and I wanted 2.4...is it just taking the download from github and replacing the files in the miner folders exactly as they are, or is there something on the back end that would prevent me in doing that? #3 is related to this...

(3)  I see when ccminer pops up that it says something at the top about "cuda 8".  I have 1080ti's that use "cuda 9", or at least that's what other miner or software versions tell me when they start (outside of HA).  Could that be causing any stability or performance issues for me? I'm not an expert so this could easily be a dumb question.

(4)  Any plans to build in some sort of maybe telegram or email notification when mining has stopped (so we can use corrective actions to fix it)?

Sorry for the long post, and while none of the above prevents me from using HA, these thoughts have been on my mind and thought I'd get them out there.

I understand it can't show me hash stats when using klaust, but is it possible to at the very least tell me the pool I am on or even the coin it's mining?

Good to hear things are working better for you. It may look a little strange, but since each device is run in its own mining process, the software can select the fastest miner for each GPU. In this case, Klaust must have better performance on the two cards while Tpruvot is faster on the third. Depending on the algorithm, the difference may or not be significant, but the software will pick the fastest unless you change the preferred miner for that device..

Okay good to know. It's pretty stable and good on cpu & gpu right now.

Edit: All 3 gpu are mining the same coin, two of gpus(1 1070 & 1 1060) has unavailable, but my 3rd gpu is showing stats. Odd

As I said before, the phrase "Mining Stats Unavailable" is not an error - it is by design due to the way the Klaust miner has been coded. As the message implies, the miner's hash rate and accepted results cannot be displayed in real-time. However, as you noted, the miner is still mining and you can see its current status in the minimized miner window.

Thank you for the reply. It's mining Substratum on AHashPool when I am seeing the error.