|
See; the extra rewards line; it is credited hashrate; thus not counting towards my hashrate. I may have found a small loophole in their system that works to our benefit.
and crackfoo; those red bars are dead pool indicators.
|
|
|
|
yep. I have it at max that nicehash allows.... I remember before zpool stratum would start below min diff nicehash allows and it would never connect... its the same as it was when Ive done rentals in the past before the major stratum issues.
The graph I showed represents about an 8% market loss, I would suspect, based on the amount of red, yours is higher. I do not run at the maximum d= allowed by NH, I use something reasonable. From this perspective: a difficulty of 8000, for a hashrate of 5-10Th, is WELL within reason. I have run 16.5K on my S7 with no issues and good hashrates reported at the pool. my machine would just never get the smaller blocks. I am trying to keep diff high so that it doesn't flood stratum with shares unnecessarily. If I try to create an order and the pool settings are wrong; the nicehash fee is forefit..... most people didnt notice that caveat. to add further; my share percentage really hasn't dipped much. it has just wavered with the hashrate that nicehash is giving me. FYI I am selling on NH for a minimum of .4BTC/Ph/day than what I am paying for their service. Kinda funny when you think of it. point hashrate at them, and get paid a little to use the hashrate by proxy. |
|
|
|
I agree it seems to be more stable than it was before. Your delta line seems more red than what I am getting and all of those dead bars seem unusual to me. Are you using a d= password parm?  yep. I have it at max that nicehash allows.... I remember before zpool stratum would start below min diff nicehash allows and it would never connect... its the same as it was when Ive done rentals in the past before the major stratum issues. *edit my S7 just dropped again.... looks like its getting pointed elsewhere; I cant be around 24/7 to reset it all the time XD |
|
|
|
had to hard reset my S7 a few min ago. But so far, pretty solid. also, you can see how much nicehash gets rejected by the pool. The extra rewards is what's offsetting it I think. Against my initial assumption I am still just about breaking even; and have generated as much as I have spent thus far. (NH fee included and considered covered first) Hope it helps. Looks like that rental will push on for another day or two...... I may top it off a little if I feel like pushing it further.  |
|
|
|
After the recent updates and tuning changes it looks like stability has improved quite a bit. Still seeing some stratum resets, but I guesstimate it's reduced 60-70%!
Still keeping an eye on it and making adjustsments so some of the resets have been intentional the past couple days.
Cheers
Ill point my S7 back at it and report back in a few days =) Thanks for the update! *edit: Also doing a 10Th rental for 24 hours to see how it compared to my older tests. I think at my rental price ill break even or loose 1-2 Mbtc... no sweat. |
|
|
|
|
yeah; Ill do that eventually... maybe.... lol
I dont think the few kb of ram is going to hurt much in the end, but eventually ill make that edit =)
|
|
|
|
well this is not correct, you are short in ORB but you have doubt against me..
Hes correct Mario; The pool only pays out in coins mined, unless you are getting payed in BTC which is the default exchange payment type for the pools account. so you only get paid in BTC, or the coins mined, as they are mined. No other way around it. |
|
|
|
Ok; I stayed out later than expected (3:00Am here) @echo off
SETLOCAL EnableExtensions
:start
cls
start /min ccminer176.exe -r 0 -a x13 -i 17.5 -o stratum+tcp://mine.zpool.ca:3633 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,d=0.004,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a x11 -i 17.5 -o stratum+tcp://mine.zpool.ca:3533 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,d=0.001,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a qubit -i 17.2 -o stratum+tcp://mine.zpool.ca:4733 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,d=0.004,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a x15 -i 17.5 -o stratum+tcp://mine.zpool.ca:3733 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,d=0.01,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a lyra2v2 -i 17.2 -o stratum+tcp://mine.zpool.ca:4533 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,d=1,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a neoscrypt -i 17 -o stratum+tcp://mine.zpool.ca:4233 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a decred -o stratum+tcp://mine.zpool.ca:5744 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,d=0.5,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a blakecoin -o stratum+tcp://mine.zpool.ca:5743 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a c11 -o stratum+tcp://mine.zpool.ca:3573 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a quark -i 17.5 -o stratum+tcp://mine.zpool.ca:4033 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a groestl -o stratum+tcp://mine.zpool.ca:5333 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a blake2s -o stratum+tcp://mine.zpool.ca:5766 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,d=0.4,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a x14 -o stratum+tcp://mine.zpool.ca:3933 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
start /min ccminer176.exe -r 0 -a x17 -o stratum+tcp://mine.zpool.ca:3737 -u 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP -p p690gtx980-
1,c=BTC,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats
:wait1
set EXE=ccminer176.exe
FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto FOUND
goto FIN1
:FOUND
echo %EXE% still running.
goto wait1
:FIN1
goto start You will have to make a loop for "SET EXE" to the multiple variants of the miner apps that you run. but for simplicity sake in what im doing, I am just trying to stick with one miner app to keep upgraded; I don't mind not using optimized and algo specific versions anymore. too much mess in the end. Be sure to use the version that is quoted a few posts above. It has support for the extended password length. If you don't have a miner app that can take the long password, you will notice multiple ports/algos will remain connected at the same time. So just download the Cuda 8.0 optimized version. For you AMD folks; sorry; I haven't stepped into that world quite yet. In Win10, I can also make live edits to the batch file and not have to close and restart anything... at the worst close the current running algo and watch em all reset. But just edit/save in notepad and its updated live (test this by editing the still running message if you really don't believe me). Before starting minimized, it was funny watching the batch poop out that many windows all at once. Be sure to have thread capability.... I am running a dual Xeon SLAED machine with 26Gb ram, so it has no issues. |
|
|
|
|
My whole perspective is to remove all middle steps. Be as close to system level and thus be the least buggy.
Simple batch logic trumps all if you are only using zpool. I personally wasn't wowed by miner control.
|
|
|
|
wow, my machine has really begin to flood the server with benchmarks XD Its that algo switching I guess.
Did you ever have plans to graph or group the results in some ways?
hey JK - have you updated your latest multi-algo scripts for your 980? I want to stretch my 980Ti soon. Thanks Yeah. I'm running everything that's worth running except myr-gr. When I get back home I'll paste the batch code. The only miner app I'm presently using is the above linked cuda 8.0 ccminer. Some algos aren't optimized, but I can live with it. It's an Asus GTX 980 4Gb. The scalar between algos should be pretty close between the 980 and TI. I also modified the batch to launch each miner instance in a separate process all at once; then the server only responds to the port it wants. With this method you don't have to wait for it to cycle through each damned algo every time  |
|
|
|
What do you guys find to be the best way for utilizing Signature Campaigns, best methods, and is it worth the time and effort?
I find the best way currently available for dealing with Signature Campaigns is to just click the "ignore" on any user that participates. If they are participating in such a campaign, then I assume that they aren't here to actually learn and share knowledge, so I'm not interested in anything they say or ask. So far, I've definitely found that taking the time and making the effort to click that "ignore" link is worth it. I find the entire forum to be more pleasant and useful now that I don't see any of the nonsense posted by Signature Campaign participants. Wow, that is one of the best posts I've seen in a long time. Funny thing is, Danny won't even see this comment of mine because I just joined this sig campaign. These campaigns have both a positive and negative impact on the community and the boards. On the positive side, it gets is an effective form of advertising for crypto-based businesses. On the downside of course it encourages campaign participants to make vacuous posts in exchange for compensation. It will be interesting to see if more and more people take Danny's approach, will the popularity of sig campaigns begin to fall? Perhaps ... Agreed. Let his ignorance blind him.... It seems he's apt to cut off his nose to spite his face.... If you look throughout my post history, it has been mostly to help or ask for help and not with minor issues either...... same as most others out there. I have found the sig campaign rewards me for giving my input and advice... in a situation where it would typically be given for free anyways. It's a win win scenario in my book. |
|
|
|
|
wow, my machine has really begin to flood the server with benchmarks XD Its that algo switching I guess.
Did you ever have plans to graph or group the results in some ways?
|
|
|
|
|
if BTC isnt worth enough by halving I believe a lot of miners will shut off hashrate and the TTF will go through the roof till the next diff correction.... that's a big IF though.
|
|
|
|
|
@AngryDwarf Thanks a million.
All issues resolved and all algos up and running. Thanks again!
|
|
|
|
cuda 8.0 Did you get this with your latest driver or something? Takes a while to download things where I am at, and I can only find dev-notes on cuda 8.0... that miner app cant detect my video card.... Ill try finding a driver without the bloat package.... edit: nope. 351mb every stupid video driver update. insane. |
|
|
|
|
nope, I used cryptominingblog.
Im going to try that one now.
|
|
|
|
Password length has been increased from 128 to 386 with ccminer 1.7.6. Should be able to get a precompiled binary on tpruvot ccminer releases github,
Thanks! Trying it now =) looks like it isnt working properly.... I think I may have downloaded the version with the smaller password even though its released as 1.7.6. Could you 7zip the ccminer.exe file and email it to me? my username at gmail. You'd have to 7zip, enable compression, and add a password so it will make it through; unless you have a file hosting service somewhere =/ Thats one of the things about github; same versions but many flavors of that one version.... annoying. |
|
|
|
Password length has been increased from 128 to 386 with ccminer 1.7.6. Should be able to get a precompiled binary on tpruvot ccminer releases github,
Thanks! Trying it now =) Crackfoo; the profitability scalar of myr-gr is in Mh/s not Gh/sec right? and can you verify for me that the server is seeing my whole password? It will be a lot less confusing to try and figure that out again... plus take waaaaaay less time.... 1PHSDYvVp6HpqtuUPocK41DrdeHbbezaeP p690gtx980-1,c=BTC,x11=8.2,x13=6.8,qubit=12.5,x15=5.6,lyra2v2=9.6,neoscrypt=0.5,decred=1.7,blakecoin=1.4,c11=8.8,myr-gr=44,quark=11.5,groestl=24.5,blake2s=1.2,x14=7.0,x17=5.2,stats |
|
|
|
|
whom here knows which precompiled Win x64 ccminer is available that has the password length size increased? (int --> long int)?
|
|
|
|
|
Show Posts
