Bitcoin Forum
December 11, 2016, 02:42:17 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   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 »
  Print  
Author Topic: [NEW POOL & MINER] - BitcoinPool.com - Jump In! ~NO FEES~ :)  (Read 96088 times)
datathe1st
Jr. Member
*
Offline Offline

Activity: 30


View Profile
March 20, 2011, 08:35:14 PM
 #321

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?

All donations (even 0.01 BTC) are much appreciated! Thank you!
13PNeVP5hNbmXVccfeC73BENtKdht2aEVe
1481424137
Hero Member
*
Offline Offline

Posts: 1481424137

View Profile Personal Message (Offline)

Ignore
1481424137
Reply with quote  #2

1481424137
Report to moderator
1481424137
Hero Member
*
Offline Offline

Posts: 1481424137

View Profile Personal Message (Offline)

Ignore
1481424137
Reply with quote  #2

1481424137
Report to moderator
1481424137
Hero Member
*
Offline Offline

Posts: 1481424137

View Profile Personal Message (Offline)

Ignore
1481424137
Reply with quote  #2

1481424137
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481424137
Hero Member
*
Offline Offline

Posts: 1481424137

View Profile Personal Message (Offline)

Ignore
1481424137
Reply with quote  #2

1481424137
Report to moderator
1481424137
Hero Member
*
Offline Offline

Posts: 1481424137

View Profile Personal Message (Offline)

Ignore
1481424137
Reply with quote  #2

1481424137
Report to moderator
m0mchil
Full Member
***
Offline Offline

Activity: 171


View Profile
March 20, 2011, 08:51:31 PM
 #322

All nonce is checked in ~7 seconds on 5870 GPU.

It's actually 12 seconds or more, but I update at whatever_nonce_exhaust_time - TIMEOUT(=5 seconds).


Line 114 - 115 of BitcoinMiner.py

Code:
self.askrate = max(int(askrate), 1)
self.askrate = min(self.askrate, 10)

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.


FairUser
Sr. Member
****
Offline Offline

Activity: 261


View Profile WWW
March 20, 2011, 10:48:54 PM
 #323

Now you can really increase effeciency to the level of other pools.
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. Smiley
It's ok, i don't mind if truth is funny for you Smiley
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. Wink
You seem like you can take it better than most.
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
March 20, 2011, 10:49:10 PM
 #324

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.

+1 agreed


Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
Wikene
Newbie
*
Offline Offline

Activity: 2


View Profile
March 20, 2011, 10:55:00 PM
 #325

Hi
Getting this om my iMac:

20/03/2011 23:50:40, d29e1a8c, accepted at 78% of getwork[13]                 
20/03/2011 23:50:42, long poll: new block                                     
[GW: 14][AR: 83][0/100%]-[kHash/s: 51038]-[Eff: 86%][I/S: 0%][Emp: 21%]Exception in thread Thread-1:
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 522, in __bootstrap_inner
    self.run()
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/Users/torsteinwikene/Downloads/poclbm-mod-03/sources/BitcoinMiner.py", line 313, in longPollThread
    if getworkCount != 0:
UnboundLocalError: local variable 'getworkCount' referenced before assignment

[GW: 14][AR: 83][87/100%]-[kHash/s: 49604]-[Eff: 86%][I/S: 0%][Emp: 21%]       



The miner continues working...
FairUser
Sr. Member
****
Offline Offline

Activity: 261


View Profile WWW
March 20, 2011, 11:13:17 PM
 #326

Guys, I really respect your hard work providing another pool. But please cut all this 'efficiency' pseudo-science.

+1 agreed

This is not "pseudo-science", it's a fact.  We spent over a month working, testing, and analyzing results. 

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.

Code:
03/20/2011 15:54:21, 666bb698, accepted at 24% of getwork[7379]
03/20/2011 15:54:29, 1eda3c61, accepted at 56% of getwork[7379]
03/20/2011 15:54:29, 5a64d0d1, accepted at 56% of getwork[7379]

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. 

Working through the entire getwork isn't a bad thing.  If you feel it is, please elaberate.
------------------------------------------------------------------------------------
http://dictionary.reference.com/browse/efficiency
Quote
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.
FairUser
Sr. Member
****
Offline Offline

Activity: 261


View Profile WWW
March 20, 2011, 11:13:39 PM
 #327

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. Wink
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. Smiley
geebus
Sr. Member
****
Offline Offline

Activity: 258



View Profile WWW
March 20, 2011, 11:39:50 PM
 #328

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. Wink
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. Smiley

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. Smiley

Feel like donating to me? BTC Address: 14eUVSgBSzLpHXGAfbN9BojXTWvTb91SHJ
geebus
Sr. Member
****
Offline Offline

Activity: 258



View Profile WWW
March 21, 2011, 02:20:02 PM
 #329

*** MINER UPDATE - 03/21/2011 ***

DOWNLOAD: poclbm-mod.03.21.2011b.zip (Win32/Linux) 7.9MB

Changes / Updates:
  • Proper tracking of the percentage of hashspace worked through.
  • Local tracking of all submitted shares prevents duplicates from being submitted.
  • "Emp." is now an integer and not a percentage
  • Resolved issue resulting in ~40% drop in submitted:requested
  • Searches as much of the hash space as possible without causing re-work.

I recommend you update ASAP.

Happy mining!

Edit: Minor fix in the code for slow clients. Askrate was being automatically capped at 55 seconds and is not anymore.

Feel like donating to me? BTC Address: 14eUVSgBSzLpHXGAfbN9BojXTWvTb91SHJ
dishwara
Legendary
*
Offline Offline

Activity: 1386

Truth may get delay, but NEVER fails


View Profile
March 21, 2011, 02:40:40 PM
 #330

*** MINER UPDATE - 03/21/2011 ***

DOWNLOAD: poclbm-mod.03.21.2011.zip (Win32/Linux) 7.9MB

Changes / Updates:
  • Proper tracking of the percentage of hashspace worked through.
  • Local tracking of all submitted shares prevents duplicates from being submitted.
  • "Emp." is now an integer and not a percentage
  • Resolved issue resulting in ~40% drop in submitted:requested
  • Searches as much of the hash space as possible without causing re-work.

I recommend you update ASAP.

Happy mining!


Nothing happens clicking the link. It just opens a empty page with this address http://bitcoinpool.com/file.php?id=4
No file is downloading on chrome, firefox, IE9
bobR
Member
**
Offline Offline

Activity: 112


View Profile
March 21, 2011, 06:43:50 PM
 #331

Why are stale messages being kicked up on a slow machine Huh
FairUser
Sr. Member
****
Offline Offline

Activity: 261


View Profile WWW
March 21, 2011, 06:50:38 PM
 #332

Nothing happens clicking the link. It just opens a empty page with this address http://bitcoinpool.com/file.php?id=4
No file is downloading on chrome, firefox, IE9

Fixed.  Thank you for reporting it.
FairUser
Sr. Member
****
Offline Offline

Activity: 261


View Profile WWW
March 21, 2011, 06:52:47 PM
 #333

Why are stale messages being kicked up on a slow machine Huh

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.
bobR
Member
**
Offline Offline

Activity: 112


View Profile
March 21, 2011, 06:59:26 PM
 #334

Why are stale messages being kicked up on a slow machine Huh

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 head
i'm usin pudinpops miner

What does long polling have to do with it

I get work ... every so often as per your edit
why should it be stale when i'/v never hashed the whole chunk
You want wait before I ask for another
my wait and hash times ... i never hash a whole chunk
Why should it go stale Huh
your pool hasn't solved a block in over 24 hrs
This makes no sense
FairUser
Sr. Member
****
Offline Offline

Activity: 261


View Profile WWW
March 21, 2011, 07:20:49 PM
 #335

Why are stale messages being kicked up on a slow machine Huh

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 head
i'm usin pudinpops miner

What does long polling have to do with it

I get ... every so often as per your edit
why should it be stale when i'/v never hashed the whole chunk
You want wait before I ask for another
my wait and hash times ... i never hash a whole chunk
Why should it go stale Huh


I don't use pudinpops miner, and I do not know if it supports long polling.  You should ask him that.
You could get jgarzik's CPU miner which does support long polling:   http://bitcointalk.org/index.php?topic=1925.0

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.



Also, it makes perfect sense why our pool hasn't found anything in 24 hours.
Put the speed of the pool into the bitcoin calculator:  http://www.alloscomp.com/bitcoin/calculator.php

The pool speed is about: 4600000 khash/s   or 4.6 Ghash/s
That comes out to:

Probability   Time
Average   19 hours, 45 minutes
50%        13 hours, 41 minutes
95%        2 days, 11 hours, 12 minutes

At the speed we're going, it could take 2 days.  Be patient.
If don't like being patient, you might want to check out another pool.
dishwara
Legendary
*
Offline Offline

Activity: 1386

Truth may get delay, but NEVER fails


View Profile
March 21, 2011, 07:22:30 PM
 #336

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.
dishwara
Legendary
*
Offline Offline

Activity: 1386

Truth may get delay, but NEVER fails


View Profile
March 21, 2011, 07:30:01 PM
 #337

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.
bobR
Member
**
Offline Offline

Activity: 112


View Profile
March 21, 2011, 07:31:58 PM
 #338

ok I think i got it
just ignore it if it pops up occasionally
geebus
Sr. Member
****
Offline Offline

Activity: 258



View Profile WWW
March 21, 2011, 10:17:44 PM
 #339

ok I think i got it
just ignore it if it pops up occasionally

I'm not so sure you did.

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.

Feel like donating to me? BTC Address: 14eUVSgBSzLpHXGAfbN9BojXTWvTb91SHJ
Drazar
Newbie
*
Offline Offline

Activity: 10


View Profile
March 21, 2011, 11:41:03 PM
 #340

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
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 »
  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!