Bitcoin Forum
August 15, 2018, 02:15:17 AM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 [46] 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 ... 375 »
  Print  
Author Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]  (Read 834289 times)
ZodiacDragon84
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250


The king and the pawn go in the same box @ endgame


View Profile
February 02, 2012, 08:34:17 PM
 #901

patience is a virtue

Looking for a quick easy mining solution? Check out
www.bitminter.com

See my trader rep at Bitcoinfeedback.com
!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534299317
Hero Member
*
Offline Offline

Posts: 1534299317

View Profile Personal Message (Offline)

Ignore
1534299317
Reply with quote  #2

1534299317
Report to moderator
1534299317
Hero Member
*
Offline Offline

Posts: 1534299317

View Profile Personal Message (Offline)

Ignore
1534299317
Reply with quote  #2

1534299317
Report to moderator
DrHaribo
Legendary
*
Offline Offline

Activity: 2436
Merit: 1019


Bitminter.com Operator


View Profile WWW
February 02, 2012, 09:13:10 PM
 #902

Welcome to our new king of the hill

1   michaelmclees   33,117

33GH, thats some serious hashing power!

looks like he left early Cheesy

He pushed up to almost 40 GH/s, then stales started rising.

What I found strange is that the new server isn't breaking a sweat, and still things slow down badly when the number of requests per second goes over a certain point. After watching the logs and numbers for a while I've located several bottlenecks in my programming. I hope to have a new version of the pool back end up sometime tomorrow. It should be able to make full use of the more powerful server.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
Turbor
Legendary
*
Offline Offline

Activity: 1022
Merit: 1000


BitMinter


View Profile WWW
February 02, 2012, 09:18:14 PM
 #903

Well it's not too bad on my side. I'm down to 0.53% for this block. It looks like the FPGA have now a lower stale rate than the GPUs. Can you add the stale rate for each worker to the worker stats ? Would be interesting for tuning.

michaelmclees
Hero Member
*****
Offline Offline

Activity: 631
Merit: 500


View Profile
February 02, 2012, 09:25:17 PM
 #904

Welcome to our new king of the hill

1   michaelmclees   33,117

33GH, thats some serious hashing power!

I threw some GPUMAX at you attempting to figure out what the use of leasing hashing power was.  I'm still clueless.   Huh
DrHaribo
Legendary
*
Offline Offline

Activity: 2436
Merit: 1019


Bitminter.com Operator


View Profile WWW
February 02, 2012, 09:34:02 PM
 #905

Well it's not too bad on my side. I'm down to 0.53% for this block. It looks like the FPGA have now a lower stale rate than the GPUs. Can you add the stale rate for each worker to the worker stats ? Would be interesting for tuning.

0.53% isn't very good. And somewhere around 160-170 GH/s stales suddenly rise a lot. Next update the back end should run much better.

Add percentages beside the rejected numbers? Good idea. I put that on my list.

I threw some GPUMAX at you attempting to figure out what the use of leasing hashing power was.  I'm still clueless.   Huh

Well, it's very useful for me. I can see how much my server can handle, and find bottlenecks in my software. Smiley

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
Turbor
Legendary
*
Offline Offline

Activity: 1022
Merit: 1000


BitMinter


View Profile WWW
February 02, 2012, 09:59:27 PM
 #906

Add percentages beside the rejected numbers? Good idea. I put that on my list.

Yes, would be cool.

michaelmclees
Hero Member
*****
Offline Offline

Activity: 631
Merit: 500


View Profile
February 02, 2012, 10:07:09 PM
 #907



Well, it's very useful for me. I can see how much my server can handle, and find bottlenecks in my software. Smiley


Wonderful.  Now just so I understand how your payout system works, for shift #1398, my score is .01260124, meaning my reward will be around 50*.01260124, which is where my expected reward comes in.  But this will only occur if the next block is found before shift #1408 ends, which will happen in about 6 hours or so.  If no block is found by then, I'll get nothing.

Question, suppose 2 blocks are found rapidly by your pool.  A block is found in shift 1500 and shift 1501.  The block in shift 1500 will be composed of the work done in shift 1490-1500.  And then for the block in shift 1501 will be paid out to the workers in shifts 1491-1501, no?  Is this how it works?
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1005


Gerald Davis


View Profile
February 02, 2012, 10:11:36 PM
 #908

Dr. H not a high priority but could you consider seperating rejects into invalids & stales.  I always assumed my cards were perfect but my backup pool is ABC Pool and I they break them out.  I was surprised to see some invalid shares not just stale ones.

It would be useful for you too.  Stales the pool is partially responsible for (prompt LP, fast getwork responses) but invalids are completely on the miner.  There is nothing a "properly functioning" pool can do that would cause a miner to get invalids.
jake262144
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
February 02, 2012, 10:25:03 PM
 #909

Yeah, I'd love to see that option as well.
ABCPool's suspiciously high invalid rates always bothered me...
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1005


Gerald Davis


View Profile
February 02, 2012, 10:42:40 PM
 #910

Now just so I understand how your payout system works, for shift #1398, my score is .01260124, meaning my reward will be around 50*.01260124, which is where my expected reward comes in.  But this will only occur if the next block is found before shift #1408 ends, which will happen in about 6 hours or so.  If no block is found by then, I'll get nothing.

Correct.

Quote
Question, suppose 2 blocks are found rapidly by your pool.  A block is found in shift 1500 and shift 1501.  The block in shift 1500 will be composed of the work done in shift 1490-1500.  And then for the block in shift 1501 will be paid out to the workers in shifts 1491-1501, no?

Correct.

Just a heads up it is not possible to "game" PPLNS.  If you do get paid for 2 blocks it would simply be luck not any mathematical advantage.  If you get paid for none it once again is just bad luck.  In the long run PPLNS ensures everyone is paid "fairly" because there is no method you can use to consistently gain a greater than average share (relative to hashing power provided).
P4man
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile
February 03, 2012, 07:29:45 AM
 #911

I threw some GPUMAX at you attempting to figure out what the use of leasing hashing power was.  I'm still clueless.   Huh

Well, it's very useful for me. I can see how much my server can handle, and find bottlenecks in my software. Smiley


I can see a few uses for it, but frankly none that would be enduring or explain all the >100% pps payout schemes propping up.

1) testing or kickstarting a pool. Has to be a small market, but completely legit and not that new (ie, no different than offering bonusses as many pools do in the early days).
2) poolhopping proportional pools, but apparently gpumax disallows that (no idea how they check that though)
3) malicious intent like a double spend attack. Although that would only be useful if you can attract a majority of the hashrate (possibly in combination with a DDoS attack to reduce overall hashrate) and even then you would only want to rent it for as long as needed to pull off the attack. Still this one scares me.
4) ponzi scheme, particularly those ones only paying out like once or twice a week.

Maybe I missed some, but whatever the use, most of these schemes do not tell you how your hashpower is used, some even clearly lie about it; I would refuse to rent my hashpower if I dont know how its used. 

jake262144
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
February 03, 2012, 03:04:30 PM
 #912

Someone shoot this damned block, please! ...or shoot me instead for I've had enough Angry
P4man
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile
February 03, 2012, 03:32:13 PM
 #913

Just use some twisted logic to make yourself believe its a good thing Smiley.
Here is how I do it: in the long run, we will not significantly deviate from the average. So all the bad luck we have now, will be compensated by yet to come luck.  Some of the impatient will have left the pool by then, and therefore the patient one's will reap even more reward Cheesy. (please, dont bore me with statistics to prove me wrong!).

Seriously, a 5+M share block is gonna happen now and then. If its followed by a second  "instant" block as we have seen a few times, suddenly it doesnt look so dramatic anymore.

Also, if it helps, A1bitcoinpool is still working on its first block, ~4.5M shares now. And its a proportional pool lol, so who in their right minds is going to mine there now? Have to feel sorry for the guys mining there.

jake262144
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
February 03, 2012, 03:54:03 PM
 #914

Whenever I try, I seem to get the glas-half-empty attitude. A voice keeps telling me "You've had your luck, partner. It's going to get a lot worse before it gets better"
uhmmm... wait, that's just my pet Raven... kindly disregard my bitching Smiley

What blows my mind it that it's A1's first block... what's the pool op doing? Sleeping? Should have killed it off like 2M shares ago.
Everyone should know when to fold and run to the hills, cut the losses.
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1005


Gerald Davis


View Profile
February 03, 2012, 04:02:10 PM
 #915

The worst thing about a new pool (or a pool after making any change) is that nagging voice saying "what is there is a bug, what if it is impossible to solve a block."
P4man
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile
February 03, 2012, 04:10:06 PM
 #916

I would hope they have the sense to test their pool on the testnet first.

jake262144
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
February 03, 2012, 04:13:49 PM
 #917

Mind you, P4, the migration was a bit hasty...  Grin
What if Doc opted to take the combat reconnaisance approach to pool server bugs?
P4man
Hero Member
*****
Offline Offline

Activity: 518
Merit: 500



View Profile
February 03, 2012, 04:17:50 PM
 #918

I was referring to A1. I have full confidence in Dr H Smiley.

jake262144
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile
February 03, 2012, 04:51:57 PM
 #919

I can't help but loathe the indaquate webforum threading...
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1005


Gerald Davis


View Profile
February 03, 2012, 05:04:26 PM
 #920

Mind you, P4, the migration was a bit hasty...  Grin
What if Doc opted to take the combat reconnaisance approach to pool server bugs?

I trust Doc.  Plus we have solved some blocks.  I was talking more A1.  They have solved no blocks.  Say it goes on ANOTHER 3 million shares just by luck of the draw..  When they hit 7.5 million shares and the pool has NEVER solved any block true or not people are going to say the pool is broken.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 [46] 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 ... 375 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!