Author

Topic: [~1000 GH/sec] BTC Guild - 0% Fee Pool, LP, SSL, Full Precision, and More - page 155. (Read 379078 times)

legendary
Activity: 1750
Merit: 1007
Yeah, I found a block.    Cheesy   Which one?

You found the most recent one.  I'll follow deepbit's format of bolding the blocks found by you when I add personal statistics to the block listing.  Should be up in the next hour or so!  Looks like the server itself is running great (no crashes in the last 14 hours).  Haven't had any new miner idles/RPC comm errors since the issue which BitLex mentioned.
hero member
Activity: 499
Merit: 500
Yeah, I found a block.    Cheesy   Which one?
legendary
Activity: 1750
Merit: 1007
well, restarting my worker was the first thing i did when i noticed that error and all shares after got rejected,
it didnt help though, new shares also got rejected (all of them), so i stopped the miner again,
then posted (actually i just wanted to post that error, then i noticed the rejects i haven't looked at before).

anyway, i might have been a victim of that spike then (just started testing ~2hours before),
will test later again. Smiley

Code:
WORKSIZE=128 VECTORS AGGRESSION=6 BFI_INT

Can you send me a PM with the worker name you used?  I'll take a look at the shares log to find out why the server was rejecting them all.
hero member
Activity: 532
Merit: 505
well, restarting my worker was the first thing i did when i noticed that error and all shares after got rejected,
it didnt help though, new shares also got rejected (all of them), so i stopped the miner again,
then posted (actually i just wanted to post that error, then i noticed the rejects i haven't looked at before).

anyway, i might have been a victim of that spike then (just started testing ~2hours before),
will test later again. Smiley

Code:
WORKSIZE=128 VECTORS AGGRESSION=6 BFI_INT
legendary
Activity: 1750
Merit: 1007
I will be home and ready to resume looking into any pool issues that rise.

The high rejection rate is VERY odd, it looks like there was a spike in rejected shares about 20 minutes ago (all my miners jumped about 15 rejects recently), as well as a communication error.

I'd recommend resetting your worker stats and/or restarting your worker just to get a fresh count.  Until the spike, my 12 workers were averaging 0.29% rejected/invalid shares over the past 8 hours.

BitLex: What settings are you using on phoenix (queue size, worksize, etc)?
hero member
Activity: 532
Merit: 505
well, it's no problem at all on other pools  Cheesy

Code:
[76.92 Mhash/sec] [508 Accepted] [0 Rejected]
same miner, same settings, different pool (in this case deepbit)
sr. member
Activity: 288
Merit: 250
testing on HD5570 XP64 Cat10.12 SDK2.2 phoenix-1.4

Code:
[11/05/2011 00:07:53] Result: b814a20a rejected
[78.23 Mhash/sec] [84 Accepted] [23 Rejected] [RPC (+LP)]Unhandled error in Defe
rred:
Unhandled Error
Traceback (most recent call last):
Failure: twisted.web._newclient.ResponseFailed: [ >]
[11/05/2011 00:08:52] Result: bdc42770 rejected
[11/05/2011 00:09:45] Result: 68ccac6a rejected
[11/05/2011 00:11:19] Result: dee1d595 rejected
[11/05/2011 00:12:57] Result: 4e9e8b9e rejected
[11/05/2011 00:13:24] Result: 16aeaea8 rejected
[11/05/2011 00:13:29] Result: fce777d3 rejected
[11/05/2011 00:14:03] Result: a6d73144 rejected
[76.15 Mhash/sec] [84 Accepted] [30 Rejected] [RPC (+LP)]

besides the error, 30% of rejected shares is quite high, i've never experienced anything that bad,
any idea about that?.



It's not the pool's fault, i'm at 3700 accepted shares and only 17 rejected using phoenix 1.46.
hero member
Activity: 532
Merit: 505
testing on HD5570 XP64 Cat10.12 SDK2.2 phoenix-1.4

Code:
[11/05/2011 00:07:53] Result: b814a20a rejected
[78.23 Mhash/sec] [84 Accepted] [23 Rejected] [RPC (+LP)]Unhandled error in Defe
rred:
Unhandled Error
Traceback (most recent call last):
Failure: twisted.web._newclient.ResponseFailed: [ >]
[11/05/2011 00:08:52] Result: bdc42770 rejected
[11/05/2011 00:09:45] Result: 68ccac6a rejected
[11/05/2011 00:11:19] Result: dee1d595 rejected
[11/05/2011 00:12:57] Result: 4e9e8b9e rejected
[11/05/2011 00:13:24] Result: 16aeaea8 rejected
[11/05/2011 00:13:29] Result: fce777d3 rejected
[11/05/2011 00:14:03] Result: a6d73144 rejected
[76.15 Mhash/sec] [84 Accepted] [30 Rejected] [RPC (+LP)]

besides the error, 30% of rejected shares is quite high, i've never experienced anything that bad,
any idea about that?.

legendary
Activity: 1750
Merit: 1007
Wow one hell of a long round. Over 12 hours now. Hopefully we get a karmic streak of awesome luck for a bit after this one.

Not that long actually.  At current difficulty with the pool hashrate rounds should AVERAGE around 16 hours (due to that 50% difficulty spike the other day).  This round (AVERAGE) would be slightly higher since the pool was not running at the current speed this whole round.  The pool is only currently operating at 11.7 gHash.  It's been creeping up all day though, so rounds should get faster and faster.

UPDATE:  Average speed has gone up another 400 mHash since the above figures were posted!
newbie
Activity: 56
Merit: 0
Wow one hell of a long round. Over 12 hours now. Hopefully we get a karmic streak of awesome luck for a bit after this one.
newbie
Activity: 56
Merit: 0
Thanks for that update. Just came here to look into that little hiccup actually.
legendary
Activity: 1750
Merit: 1007
Just posting in anticipation for those who just experienced miner idles:  Added another index to the shares database to speed up the calculation of worker hash speeds (was taking way longer than it should), which caused new work to be slowed for about 90 seconds.  It cut the time it took to calculate hash speeds down to less than 1/20th what it used to be, which will be noticeable as more and more workers enter the pool.
full member
Activity: 170
Merit: 100
Will do.  Current list of improvements to be implemented tonight (PST time zone, so morning for some of you):
  1) Hide Workers
  2) Rename workers
  3) Reset worker password
  4) Optional email field for password recovery [and eventually for idle miner warnings]
  5) Optional SMS # field [will be used for password recovery and idle miner warnings once implemented]
  6) Personal block statistics included in the block listing [shares and reward]
  7) API settings to set what information the API reports

Wow! Perfect.
With all those features, this pool will be the best of all the pools out there!  Cool
legendary
Activity: 1750
Merit: 1007
Great! I look forward to seeing those features.
The hide workers thing sounds good. How about being able to rename workers?

Will do.  Current list of improvements to be implemented tonight (PST time zone, so morning for some of you):
  1) Hide Workers
  2) Rename workers
  3) Reset worker password
  4) Optional email field for password recovery [and eventually for idle miner warnings]
  5) Optional SMS # field [will be used for password recovery and idle miner warnings once implemented]
  6) Personal block statistics included in the block listing [shares and reward]
  7) API settings to set what information the API reports
full member
Activity: 170
Merit: 100
Great! I look forward to seeing those features.
The hide workers thing sounds good. How about being able to rename workers?
legendary
Activity: 1750
Merit: 1007
Those "premium services" sound great. I changed my donation level to 2.5%  Grin

One thing I would like to see is how many shares I contributed and what my payout was for each found block.
Also, being able to delete workers would be nice.

I'll be adding those stats to the block statistics this evening, as well as a hide worker.  Hidden workers won't appear in the list, or in the API, but their data will still be present if you wish to re-enable them.  That way the historical data is kept intact for all work done since the pool started.
full member
Activity: 170
Merit: 100
Those "premium services" sound great. I changed my donation level to 2.5%  Grin

One thing I would like to see is how many shares I contributed and what my payout was for each found block.
Also, being able to delete workers would be nice.
legendary
Activity: 1750
Merit: 1007
The amount is put directly into confirmed rewards, and is available even if the block is later found invalid.

http://www.bitcoinpool.com/ has an invalid block rate of 3,5%, so in essence you offer better conditions than bitcoin itself!

Might I suggest to just have a very short wait time instead of direct payout? The system you suggest would benefit the miners more than you as the pool operator and would probably eat up your ~1% profit that transactions make up currently (or even more).

At the current model a miner would be stupid or very risk loving not to pay the 2,5%, as you have a loss of ~3,5% in the form of invalid blocks anyways (didn't find statistics from the other pools on the spot...)

I know bitcoinpool had quite a few invalids early on when they first started but haven't had as many recently.  Deepbit offers the same invalid protection as part of their 3% fee as well, and I doubt Tycho would keep running it if he was losing money.  As a smaller pool the risk is greater for me, but I think by offering these services at competitive rates I can make the pool grow fast enough to reduce that risk.

If the invalid rate is causing me to lose money to the point I'd have been better off mining personally at Deepbit/slush, I may adjust the instant rate higher (to cover myself on invalids), and then add a lower tier donation to receive payouts at 2 confirmations.
legendary
Activity: 2618
Merit: 1007
The amount is put directly into confirmed rewards, and is available even if the block is later found invalid.

http://www.bitcoinpool.com/ has an invalid block rate of 3,5%, so in essence you offer better conditions than bitcoin itself!

Might I suggest to just have a very short wait time instead of direct payout? The system you suggest would benefit the miners more than you as the pool operator and would probably eat up your ~1% profit that transactions make up currently (or even more).

At the current model a miner would be stupid or very risk loving not to pay the 2,5%, as you have a loss of ~3,5% in the form of invalid blocks anyways (didn't find statistics from the other pools on the spot...)
legendary
Activity: 1750
Merit: 1007
Great solution, offering "premium services" like that for a higher fee, but still keeping the choice at the "customer"!  Smiley

Would it pay out all of my money or only the money I earned for that 2,5% donation block?
(Example: I have 100 BTC confirmed and now set my donation over 2,5%, earning me 1 BTC - do I get 101 BTC or 1 BTC directly?)

Your confirmed total includes the complete reward from your 2.5% blocks (example:
  A block is completed and your total reward for the block was 4.  You had a donation set at 3% (0.12), so the total amount you will receive is 3.88.  You can withdraw the full 3.88 immediately, without waiting for 120 confirmations.  The amount is put directly into confirmed rewards, and is available even if the block is later found invalid.

  When you click the 'Pay Me Now' button, your entire confirmed balance is sent to you, so if you had another 15 BTC in your confirmed balance before the 3.88 block, your payout will be 18.88 when you click the button.

  This weekend I'll be setting up an hourly automatic payment script so you can receive your BTC whenever it reaches 'X' amount, or every 'X' hours, depending on your preference.  The feature will be another "premium service" for anybody with donations over 1% in the previous 24 hours.  This won't be an additional 1%, so if you're already donating 2.5% you will get this service as well.
Jump to: