Slush - 2% commission = around 50 BTC per day, whereas paying for a dedicated server only costs around 100 BTC per MONTH.[Tycho] - 3% commission, but he supports long polling and you do have the option of being paid immediately instead of waiting for 120 confirmations.Geebus - 0% commission + long polling support - Really everyone should be on here pushing the average work time down and making it the best of the three pools.

Yes, we're sure. If you use more than 10 seconds for the askrate, it will force a maximum of 10 seconds.

There is a separate independent update mechanism since LP was introduced. 'self.askrate' takes place only when LP is off.

Guys, I really respect your hard work providing another pool. But please cut all this 'efficiency' pseudo-science. There is no correlation between searching whole 'nonce space' and the results you find. Yes, it affects server load, but there are other methods to solve this.

ROFL. You're funny. Please prove that statement and post the # of getwork request and # of submitted shares (which you already do) for each round on your site, and that will show the efficiency of your pool.I'll show you mine if you show me yours....oh wait....we already do show that.

It's ok, i don't mind if truth is funny for you I was talking about mining efficiency, not the getworks/shares proportion (which is not important for miners).

Oh I wasn't offended. I just like giving people shit sometimes, and I totally knew what you meant. You seem like you can take it better than most.

Guys, I really respect your hard work providing another pool. But please cut all this 'efficiency' pseudo-science. There is no correlation between searching whole 'nonce space' and the results you find. Yes, it affects server load, but there are other methods to solve this.

There is no correlation between searching whole 'nonce space' and the results you find.

I'm not sure what you're trying to correlate, but we never said you get more or less shares/nonces using this miner vs yours. In fact, you get about the same number of them in a given amount of time, but ours does it with less getwork requests. That's all we're saying. I'd love to see any data you have proving your statement, cause we have LOTS of results to prove ours. Besides, I like being able to find more than one nonce in a single getwork request. It happens quite often too.

Yes, it affects server load, but there are other methods to solve this.

What other methods would you propose?

BTW, thanks for the code. We didn't want to tell you how to manage your miner, hence why we forked it and did our own. Have you looked at the changes at all?

We did all of this because slush started charging people a "forced donation" or a fee under the notion that his amount of used resources was too high and he needed to cover the cost. So we looked into why the usage of resources was so high, and excessive getwork request end up costing him $$$ on his VPS provider. The tweaks we made to your miner would help slush, but he said he didn't want it and likes his miners using a askrate of 1 second (causing a flood of getwork), so we launched our own pool instead of complaining about it.

Our goal wasn't to 'find more faster' or anything like that, we simply wanted to be more efficient about the way our miner worked with the pool. We don't see the need to excessively call to a server for a new getwork every 10 seconds. Now with long polling, their really is no need for that type of behavior.

ef·fi·cien·cy [ih-fish-uhn-see] Show IPA–noun, plural -cies.3. the ratio of the work done or energy developed by a machine, engine, etc., to the energy supplied to it, usually expressed as a percentage.

Slush - 2% commission = around 50 BTC per day, whereas paying for a dedicated server only costs around 100 BTC per MONTH.[Tycho] - 3% commission, but he supports long polling and you do have the option of being paid immediately instead of waiting for 120 confirmations.Geebus - 0% commission + long polling support - Really everyone should be on here pushing the average work time down and making it the best of the three pools.

Is there something I'm missing?

++

But I would call it BitcoinPool, not Geebus. Technically it's in my house, but Geebus and I both work on it and regularly bounce ideas off of each other. It's a team effort.

Slush - 2% commission = around 50 BTC per day, whereas paying for a dedicated server only costs around 100 BTC per MONTH.[Tycho] - 3% commission, but he supports long polling and you do have the option of being paid immediately instead of waiting for 120 confirmations.Geebus - 0% commission + long polling support - Really everyone should be on here pushing the average work time down and making it the best of the three pools.

Is there something I'm missing?

++

But I would call it BitcoinPool, not Geebus. Technically it's in my house, but Geebus and I both work on it and regularly bounce ideas off of each other. It's a team effort.

I would likewise say the same. BitcoinPool is a 50/50 effort between FairUser and I, and it would be doing a disservice to either of us to say different. But, aside from that, I like your post.

The block is changing before you find a share. This is why we recommend that people start using long polling with our server, so that wouldn't happen.

Again you are talkin above my headi'm usin pudinpops miner

What does long polling have to do with it

I get work ... every so often as per your editwhy should it be stale when i'/v never hashed the whole chunkYou want wait before I ask for another my wait and hash times ... i never hash a whole chunkWhy should it go stale your pool hasn't solved a block in over 24 hrsThis makes no sense

The block is changing before you find a share. This is why we recommend that people start using long polling with our server, so that wouldn't happen.

Again you are talkin above my headi'm usin pudinpops miner

What does long polling have to do with it

I get ... every so often as per your editwhy should it be stale when i'/v never hashed the whole chunkYou want wait before I ask for another my wait and hash times ... i never hash a whole chunkWhy should it go stale

The bitcoin network has a "block count". This "block count" changes anytime someone finds an answer for the current block.A share is a *possible* answer for the block. If the block count of the bitcoin network increases, and your mining is still working on finding an answer for the older block, it has become stale.So the idea behind long polling is that when the block count increases, it will notify your miner right away, and then your miner starts working on the new getwork instead of the old one.

Or to put it another way, your "getwork" request may have a share (answer), and that answer may solve the current block. If it takes you too long to find an answer on your current getwork, it will go stale when the block count increases on the network. The only reason the block count increases is because someone found an answer for the block. A share can become stale at any moment, so you are literally racing against time. If you want to find more shares, you need to get a good ATI video card. It sounds like your CPU just isn't cutting it for you.

A share you got to solve which is a small part of a very large block.you solve the share & you submit it, the server checks the share you submitted is from which block.If the block you got the share has been solved even before you submitted the share, then server rejects your share saying, its stale or invalid.Every 10 minutes a block is released in the network.So, the share will become stale if you are solving very slowly, that is low hash/s.All users get stale shares, even the one who has more hash/s. But low hash/s users get more, because, they don't no yet that the share they are trying to solve is already solved by the network & 50 coins sent to them.Long polling tells the miner that a new block is released, so leave the current share & get new share.

I am not that good in understanding the backgrounds & basis of mining, so i may be wrong.Correct some one, if i am wrong.

wow >250% EFF, really unbelievable. But the saying "DUPLICATE NOT SUBMITTED" makes me feel both good & bad that i mined same share 2 times in same time(like giving birth to twins) & one is rejected, coz its a duplicate.

It's true that you can ignore it and it wont affect your mining, but the point of that whole explanation by FairUser was that you should get a different miner that supports long polling so that you're not repeatedly trying to send old answers for old work because your miner is always a step behind everyone else.

Really new to bitcoins in general and no knowledge or programming, decided to join you're pool and downloaded Kiv's version so as to not deal with it but been having very low efficency ratio's, 9% atm and wondering if there's any suggestions on how to increase it, have tried adding the -workrefershms=20000 and -d for the extra flags but both stopped it from working, currently running with -v and -w128 on my geforce 9600gt at about 9-10 Mhash/s but wondering if anyone has any suggestions for increacing my efficency