▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!KAWPOW!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂ - page 220.

crackfoo

legendary

Activity: 3570

Merit: 1126

Quote from: Storx on June 26, 2017, 12:47:39 AM

Quote from: guytechie on June 26, 2017, 12:30:04 AM

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

I just bumped the starting diff to 64 from 8.

guytechie

hero member

Activity: 677

Merit: 500

Quote from: Storx on June 26, 2017, 12:47:39 AM

Quote from: guytechie on June 26, 2017, 12:30:04 AM

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

What is a good difficulty to set to for 6.8 Mh/s?

Also, how would you modify Nemosminer 2.0.4 PowerShell script to incorporate that just for hmq1725?

JaredKaragen

legendary

Activity: 1848

Merit: 1166

My AR-15 ID's itself as a toaster. Want breakfast?

problem with doing that and leaving equihash in the password string is the pool still can try and switch you to it; when its not connecting.... unless the stratum not connecting only happens after its been mining equihash for a bit..... then it could be a viable solution.

Storx

full member

Activity: 322

Merit: 233

Quote from: Storx on June 25, 2017, 12:11:35 PM

i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect

I have managed to fix the issue i posted earlier on equihash with a band aid tell server side figures out connection issues... i added --eexit 3 to the miner, which moves on to the next algo if it fails to reconnect after 3 trys

Storx

full member

Activity: 322

Merit: 233

Quote from: guytechie on June 26, 2017, 12:30:04 AM

hmq1725 reporting low hash rate again.

I think the issue your having is the same i was having.. it starts off to low in dif, literally thousands of pieces being processed at once.. once i moved my diff up on the miner, it slowed it down and started reporting correctly... some reason the algo starts off in a super low diff and gets stuck there.. for me it was processing like 5600 sections per second at one time.. so you would get this spamming list of accepted completions.. also many were rejected due to bandwidth clutter to the cpu...

guytechie

hero member

Activity: 677

Merit: 500

hmq1725 reporting low hash rate again.

cashen

sr. member

Activity: 434

Merit: 251

I moved all my scrypt until pool issues get resolved.

Storx

full member

Activity: 322

Merit: 233

i disabled equihash on all my rigs.... it keeps loosing connection to server randomly for upwards of an hour and reconnects seem to take forever, but oddly closing the miner and restarting it fixes the issue until next disconnect

AK74XXX

newbie

Activity: 30

Merit: 0

Oh. sry, I'm new to bitcointalks, don't know where to search first

Btw, couldn't find the answer: is there a way to make so-called "NiceHash/1.0.0" miner (bought hashpower) to connect w/xnsub? If I got the idea correctly, in some cases that could reduce NiceHash switching charges.

crackfoo

legendary

Activity: 3570

Merit: 1126

Quote from: AK74XXX on June 25, 2017, 11:56:12 AM

Hey, what happened to MonetaryUnit (MUE)

I disappeared from everywhere at one moment, but looks like alive unseen: blocks are being found, transactions confirmed, balances updated... but unpaid. WTF, plz?

How about you follow the mue thread? Coins are being swapped. When they are, things will resume.

AK74XXX

newbie

Activity: 30

Merit: 0

Hey, what happened to MonetaryUnit (MUE)

It disappeared from everywhere at one moment, but looks like alive unseen: blocks are being found, transactions confirmed, balances updated... but unpaid. WTF, plz?

cashen

sr. member

Activity: 434

Merit: 251

As stated yesterday, something is going on with scrypt. Maybe its a coin the pool doesnt like. There is no way I should have 16% reject shares. my machines show solid 504MH each. The pool isnt even showing each worker.

guytechie

hero member

Activity: 677

Merit: 500

BTW, is there a condition where the pool will ignore the difficulty? Equihash is always set to 127 no matter what I put in the password.

guytechie

hero member

Activity: 677

Merit: 500

hmq1725 Is working fine again. Seeing the hasrate back (and the share % is back up).

So when it was defective, the pool only saw hashrates in the kh/s range (60-100 kh/s) and I was getting only around 0.1- 0.2% of the shares. Also, finding blocks took forever.

Now, I see 13.7MH/s (still not the full 15.5 MH/s as I'm seeing on my miner) but my share is now in the 2.6% area and blocks found much faster.

I don't think it's just a graphing problem.

icolsuineg

full member

Activity: 196

Merit: 100

Quote from: Jaerin on June 24, 2017, 06:46:30 PM

The height of the red rejects is on a different scale than the rest of the graph. I've noticed that even 1 or 2 rejected shares will create a very large spike on the graph even though it is only a couple rejected shares.

And there is the number in the right corner Wink

90.6%

guytechie

hero member

Activity: 677

Merit: 500

Quote from: Storx on June 25, 2017, 12:25:12 AM

for multi-algo,

SET PASS format for equihash is in ksol correct? so if the miner reports 4242sols, i place it in the SET PASS line as 4.242 correct? just trying to fine tune some errors i may have made... noticed that i have been mining non-stop equihash all day since adding it to my multi-algo switcher batch

That seems right to me, but might want to round it to less digits if it doesn't seem to work right. Maybe to 4.24 or 4.2

Storx

full member

Activity: 322

Merit: 233

for multi-algo,

SET PASS format for equihash is in ksol correct? so if the miner reports 4242sols, i place it in the SET PASS line as 4.242 correct? just trying to fine tune some errors i may have made... noticed that i have been mining non-stop equihash all day since adding it to my multi-algo switcher batch

JaredKaragen

legendary

Activity: 1848

Merit: 1166

My AR-15 ID's itself as a toaster. Want breakfast?

Quote from: Jaerin on June 24, 2017, 06:46:30 PM

The height of the red rejects is on a different scale than the rest of the graph. I've noticed that even 1 or 2 rejected shares will create a very large spike on the graph even though it is only a couple rejected shares.

Still something that should be investigated if possible

It's simple. Hashrate makes the graph 0-2gh let's say. the rejects are a flat 0-100 scale. I think the vertical scale is staying matched with the hashrate display instead of its own 0-100%.

shotgun1969

hero member

Activity: 723

Merit: 501

you guys have to realize somewhere somehow some graphing dev is sitting back lhao. Grin

Jaerin

full member

Activity: 154

Merit: 100

The height of the red rejects is on a different scale than the rest of the graph. I've noticed that even 1 or 2 rejected shares will create a very large spike on the graph even though it is only a couple rejected shares.

Still something that should be investigated if possible

Topic: ▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!KAWPOW!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂ - page 220. (Read 279744 times)