Topic: [ANN] profit switching auto-exchanging pool - www.middlecoin.com - page 149. (Read 829908 times)

+1

Especially on a wireless network you do for generic surfing.

If you MUST use a wireless network; get a separate router and have it on a separate channel with a completely different IP setup, etc. to reduce broadcast traffic.

The easiest way to lower rejects is to ping each one of the servers and choose 2 or 3 with the lowest ping... Add the lowest as primary and the other as failover-only.

Wait for an hour and then monitor your miner to see what's the percentage of rejected shares. Rotate the servers above if needed until you get it.

AND NEVER USE WIRELESS ... unless you can not mine otherwise

Seriously speaking though, I am starting to learn, Thanks to everyone for the advice, Including dgross0818 and yourself.

Blissfully ignorant, too.  

*popcorn*

Probably not a different pool, just a screwed up config somewhere. I've done it myself, forget to include the right --scrypt setting on a card or two and they start reporting crazy high hash rates locally while submitting nothing but nonsense to the pool. It's easily done. And also easily corrected with some diligence.

So what you're saying is I'm an unlucky bastard ? 

The graphs on Middlecoin are based souly on shares submitted ? Because that would give me an idea why I've lost "Power" if you like , So no ideas on how to reduce rejects ? Because I'm sure I don't , I've tried everything, Lowering intensity, Clocks, All sorts of settings.

As pointed out above, the difference between your local hashrate (what you see on your rigs) and the rate reported on Middlecoin (or any 3rd party graph) is due to your "luck" in the number of shares your workers solve

If I have a card that is hashing at 600 kH/s, I can expect it to solve a block of X difficulty in time T (the concept is way more important than the numbers in this example)

Sometimes that card will get "lucky" and solve the block a lot faster than "average"... other times it may take 5 times as long to solve a block of the same difficulty

I have a laptop with a pretty lame hashrate of 135 kH/s... with a pool difficulty of 1024, it "should" solve a share every 7-8 minutes or so (It's late and I probably messed that up) however, I've had times when it solved in 2 min, and others when I've gone 15 minutes without an accepted share.

When your cards solve blocks faster than "normal" your hashrate can actually be reported higher than it actually is, as all Middlecoin is doing is counting the number of accepting shares over a period of time, factoring in the difficulty, and then spitting out the hashrate that corresponds.

With a low pool difficulty of 64 (for example) you can expect to submit roughly 16 times the number of shares vs a pool with difficulty 1024.

In statistics, we use the Law of Large Numbers to explain how as the number of samples increases, the average result should converge, with a variance decreasing to 0 as the number of samples gets infinitely large.

With a lower diff pool, you are submitting enough shares, even with a "slower" rig that the hashrate should be fairly accurate over a period of time as short as an hour or two. When you combine a slower rig with a high-dif pool like MC, the hashrate can be over or under reported drastically when the sample time is so short.

This is why we keep saying please compare your daily average hashrate to what your miners are reporting locally. Obviously if your uptime is less than 24 hours you will need to multiply the local hashrate by (hours up during past 24 hours / 24) (The fraction of time the rig was online)

If you are still seeing an issue, then it's most likely due to not factoring in the shares you lost through stales/rejects. If it's still wrong, then most likely your WU units are substantially lower than your reported hashrate, potentially due to a bad graphics card config, latency, wrong server, crows nesting nearby, etc

Sounds about right lol

For this sir, you win the internet for the day! Purely because it reminded me of that track, and now I too am humming it....

It's a holiday in Cambodia
Where people dress in black
A holiday in Cambodia
Where you'll kiss ass or crack

H20 haz been stealing my 0.65 M/Hz hash rate and you LOZERS!1! are all followen' him blindly.

DON'T YOU SEEZ THE GRAPHESSSSS!!!

DON'T YOU!!!!



AS you can CLEARLY SEE, my 0.65 M/Hz hashz rate is NO WHERE TO BE SEEN

H20!!!! THEIFFFFF

WHERE'Z MY BITCOIN!!!!!

It's not irrelevant. There is a direct correlation between hash rate and shares submitted. More hash rate, more shares, higher payout.

If you deconstruct it, payout is measured by shares.  Shares, however, are not measured by hashrate.  To give you a reading, pool operators provide a metric that shows you what hash rate on average would submit the shares at the rate in which your miner is currently submitting shares.  

Efficiency levels?  Get your stales and rejects down.  I don't know why they are so high on this server.  H20 doesn't know either last time I checked, and that is much more important for him to work on than to explain to everyone on here how mining works.  

So your saying the hash rate is irrelevant , It's the shares submitted, Ok any pointers on how to increase my efficiency levels ?

Toss in a scammer accusation and a referral to SimonG's mythical pay-to-play invitation-only pool, and I believe I'm good 

Everyone has been getting huge amounts of rejects lately, God only knows why.

Which server is your pool connected to? Try a different middlecoin.com server and see if that changes things for you. Check the main website and see which one is geographically closest to you.

Could everyone give me an idea on their efficiency levels and what sort of expiry settings they have in CGWatcher etc please , It may help

I suddenly have a lot of rejects... not sure why this is. My configuration hasn't changed, and in fact my internet connection is better than it ever has been before.

Please can anyone halp?

http://www.middlecoin.com/reports/1KkfPxwQTsTawfuFgPxn78DuVvdJUxpcvv.html is me