Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 62. (Read 499597 times)
September 05, 2012, 01:42:38 PM
Strange my reject was .1% and my overall difficulty was 1.548 overnight. Some shared did bleed over to US3 not variable but I setup a different worker for variable so that only that worker on the variable server uses it. All in all I think it works pretty good at 864mHs.
September 05, 2012, 06:19:40 AM
After running cgminer all night at 200 MH/s, WU reports 3.0. I generally saw 2.9 in the past. It's interesting I'm not sure what it means.
I noticed a higher than average reject rate however. Usually I get like less than 0.5% rejects but overnight it was 1.09%
I noticed a higher than average reject rate however. Usually I get like less than 0.5% rejects but overnight it was 1.09%
September 05, 2012, 05:11:01 AM
Yep now with different difficulty shares, U now only means exactly what it's name is - shares per minute - but can't be compared to hash rates and with variable difficulty shares it makes it even harder to compare it to anything.
The number of interest on your screen is WU:
At 799MH/s you would expect a WU: of 11.16/m per BFL
You are getting 22.5/m for 2 BFL's so doing a small bit better due to luck.
The actual payout will be less than 22.5/m since 22.5/m includes rejected shares.
Unfortunately you don't know what those 11 rejected shares were - so you can only estimate them.
If Avg Diff is a true weighted average then 11 shares estimates to 27.7 diff 1 shares rejected out of the total.
... I've got no idea if it is a true weighted average - though of course Inaba should know - he wrote it
You can get the total shares sent to the pool from the API in 2.7.1 and later
(it's currently called 'Diff1 Shares' with the 'pools' API command - I've changed it to 'Diff1 Work' for the next release)
Or by multiplying WU: (if you only have one pool) times the elapsed time cgminer has been running.
Every time I see this I think the API needs a diff1 version of Accept, Reject, Stale ... to be added into cgminer ...
The number of interest on your screen is WU:
At 799MH/s you would expect a WU: of 11.16/m per BFL
You are getting 22.5/m for 2 BFL's so doing a small bit better due to luck.
The actual payout will be less than 22.5/m since 22.5/m includes rejected shares.
Unfortunately you don't know what those 11 rejected shares were - so you can only estimate them.
If Avg Diff is a true weighted average then 11 shares estimates to 27.7 diff 1 shares rejected out of the total.
... I've got no idea if it is a true weighted average - though of course Inaba should know - he wrote it
You can get the total shares sent to the pool from the API in 2.7.1 and later
(it's currently called 'Diff1 Shares' with the 'pools' API command - I've changed it to 'Diff1 Work' for the next release)
Or by multiplying WU: (if you only have one pool) times the elapsed time cgminer has been running.
Every time I see this I think the API needs a diff1 version of Accept, Reject, Stale ... to be added into cgminer ...
September 05, 2012, 12:43:59 AM
Dave3: Those look in line with my testing. Your speed reads a little high, but it's hard to gauge with only 15 minutes of testing. How does it look after a couple hours? What is your time estimation window set at?
The "Minutes to estimate miner Hashrate" is set to 15.
Here's an updated screenshot after it's been running longer.
Code:
cgminer version 2.7.5 - Started: [2012-09-04 13:44:23]
--------------------------------------------------------------------------------
(5s):1918.5 (avg):1597.9 Mh/s | Q:2601 A:11027 R:11 HW:0 E:424% U:8.0/m
TQ: 0 ST: 3 SS: 0 DW: 622 NB: 165 LW: 53329 GF: 1 RF: 0 WU: 22.5
Connected to http://us3.eclipsemc.com:8437 with LP as user ---
Block: 000005c839363eeee11f2a13eb0140d8... Started: [12:33:53]
--------------------------------------------------------------------------------
[P]ool management [S]ettings [D]isplay options [Q]uit
BFL 0: 58.2C | 810.8/799.0Mh/s | A:5478 R:7 HW:2 U: 3.99/m
BFL 1: 60.1C | 811.0/798.9Mh/s | A:5549 R:4 HW:0 U: 4.04/m
--------------------------------------------------------------------------------
[2012-09-05 12:31:53] Accepted 084073e0.55146c0e BFL 0 pool 0
[2012-09-05 12:32:04] Accepted 0192a157.deea61ea BFL 1 pool 0
[2012-09-05 12:32:04] Accepted 3bd8a050.a7007231 BFL 0 pool 0
[2012-09-05 12:32:09] Accepted 209b5323.7481b00e BFL 1 pool 0
[2012-09-05 12:32:09] Accepted 13eac2c7.c8bb0af5 BFL 1 pool 0
[2012-09-05 12:32:25] Accepted 4c13f434.ba7d8adc BFL 1 pool 0
[2012-09-05 12:32:35] Accepted 545fb2cf.08271d9f BFL 1 pool 0
[2012-09-05 12:32:57] Accepted 48c16c81.7c6d0cb7 BFL 0 pool 0
[2012-09-05 12:33:02] Accepted 2ece305f.5b90efe5 BFL 0 pool 0
[2012-09-05 12:33:07] Accepted 4112cb7d.9a1f879f BFL 1 pool 0
[2012-09-05 12:33:18] Accepted 3a85fbe6.7a73650f BFL 1 pool 0
[2012-09-05 12:33:18] Accepted 0a681ce3.4fe75564 BFL 0 pool 0
[2012-09-05 12:33:23] Accepted 3fc58053.6b5f6a17 BFL 1 pool 0
[2012-09-05 12:33:34] Accepted 4ff968b4.0509ef36 BFL 0 pool 0
[2012-09-05 12:33:34] Accepted 18728d1c.981676a4 BFL 0 pool 0
[2012-09-05 12:33:44] Accepted 1d3777db.7e26ecd3 BFL 1 pool 0
[2012-09-05 12:33:49] Accepted 01fc850d.ac37531e BFL 1 pool 0
[2012-09-05 12:33:53] LONGPOLL from pool 0 detected new block
[2012-09-05 12:33:59] Accepted 0a5bff2c.c71a112f BFL 0 pool 0
[2012-09-05 12:34:09] LONGPOLL from pool 0 requested work restart
[2012-09-05 12:34:20] Accepted 192a694d.a3e0ad10 BFL 1 pool 0
[2012-09-05 12:34:30] Accepted 30dbe2a9.05a6dcec BFL 1 pool 0
[2012-09-05 12:34:36] Accepted 09114230.b65e226a BFL 1 pool 0
[2012-09-05 12:35:03] BFL0: Error: Send work reports: NONCE-FOUND:C7ADA7B3
[2012-09-05 12:35:05] BFL4: Garbled response probably throttling, clearing buffer
[2012-09-05 12:35:08] BFL0: Comms error
[2012-09-05 12:35:34] Accepted 0f81fe2c.f740e9e2 BFL 1 pool 0
[2012-09-05 12:35:41] Accepted 232d3f68.dbf5ca28 BFL 0 pool 0
[2012-09-05 12:35:44] Accepted 2c2ef302.6c35d5bf BFL 1 pool 0
[2012-09-05 12:35:46] Accepted 32fb27d8.a34e2c76 BFL 0 pool 0
[2012-09-05 12:36:02] Accepted 375b5ba0.742c5e64 BFL 0 pool 0
[2012-09-05 12:36:13] Accepted 064eb8bc.c16ab480 BFL 0 pool 0
[2012-09-05 12:36:18] Accepted 390daca5.c39d7158 BFL 0 pool 0
[2012-09-05 12:36:23] Accepted 175e562b.a4209fca BFL 0 pool 0
[2012-09-05 12:36:32] Accepted 1e3a81a8.ac078e23 BFL 1 pool 0
[2012-09-05 12:36:59] Accepted 4214dbe9.47f07dc6 BFL 1 pool 0
September 04, 2012, 09:25:29 PM
"my 200 MH/s "rig""
I LOL'd
Sorry man, but as a small (slow) miner myself I found this funny.
I LOL'd
Sorry man, but as a small (slow) miner myself I found this funny.
September 04, 2012, 08:04:03 PM
I switched my 200 MH/s "rig" over to us3 to test variable diff. Unsurprisingly my miner stats say 1.
I did notice that cgminer is reporting a higher WU than I'm used to seeing. I usually get around 2.9 but it's 3.2 right now. Maybe I just hit a lucky streak.
I'll report tomorrow morning after running it all night.
I did notice that cgminer is reporting a higher WU than I'm used to seeing. I usually get around 2.9 but it's 3.2 right now. Maybe I just hit a lucky streak.
I'll report tomorrow morning after running it all night.
September 04, 2012, 08:00:15 PM
Yes, it works on the same time frame window as your hashrate estimate, which is found in the lower left hand corner of your My Account page
September 04, 2012, 07:58:12 PM
Oh, does it zero after a time?
I was expecting it to maybe reset every round or something
I was expecting it to maybe reset every round or something
September 04, 2012, 07:33:15 PM
The only way that can happen is if you stop submitting shares to any server. Is the avg difficulty still giving you problems?
September 04, 2012, 06:58:18 PM
Also trying the vardiff server.
Seems to be working OK, but the avg diff readout has stopped working... stuck at 0.
Seems to be working OK, but the avg diff readout has stopped working... stuck at 0.
September 04, 2012, 06:19:12 PM
To be specific, it's the 2nd part of the 2 part pair of roll-n-time and >diff1 shares
Roll-n-time means you ask the pool for work and can make multiple work items with the one work item you get from the pool
Typically it seams around 10 or 20 work items per single work request for someone in the 1GH/s to 2GH/s range.
Thus you are asking the pool for 1/10th or even 1/20th of the information, thus your requests to the pool for work are also 1/10th or 1/20th of the bandwidth
... and the pool has to do 1/10th or 1/20th of the getwork work for you that it needs to do without roll-n-time.
However, you still find the same number of shares and thus have to send back a share for each one to the pool.
Higher difficulty shares means you are telling the pools you have done more work, so you get paid for more work, each time you send a share back to the pool.
An example would be 2 diff shares.
A 2 diff share means you will only find half as many as you would if you were looking for 1 diff shares.
Since you only find half as many, they get paid twice as much.
As a result, you are also only sending half as many shares to the pool - so again you are using half as much bandwidth sending shares to the pool and the pool only has to handle half as many shares processing ... from you.
However, there is of course also a down side to >1 diff shares, it increases your variance.
However, anyone mining with a high hash rate is already mining with a lower variance than people with a low hash rate - so it's not really a negative thing in that respect - as long as the difficulty shares you are getting are appropriate for your hash rate.
See the posts by the BTC Statistics Squad for details about what difficulty shares are appropriate for your hash rate
(of course I am referring to people like organofcorti and Meni )
Roll-n-time means you ask the pool for work and can make multiple work items with the one work item you get from the pool
Typically it seams around 10 or 20 work items per single work request for someone in the 1GH/s to 2GH/s range.
Thus you are asking the pool for 1/10th or even 1/20th of the information, thus your requests to the pool for work are also 1/10th or 1/20th of the bandwidth
... and the pool has to do 1/10th or 1/20th of the getwork work for you that it needs to do without roll-n-time.
However, you still find the same number of shares and thus have to send back a share for each one to the pool.
Higher difficulty shares means you are telling the pools you have done more work, so you get paid for more work, each time you send a share back to the pool.
An example would be 2 diff shares.
A 2 diff share means you will only find half as many as you would if you were looking for 1 diff shares.
Since you only find half as many, they get paid twice as much.
As a result, you are also only sending half as many shares to the pool - so again you are using half as much bandwidth sending shares to the pool and the pool only has to handle half as many shares processing ... from you.
However, there is of course also a down side to >1 diff shares, it increases your variance.
However, anyone mining with a high hash rate is already mining with a lower variance than people with a low hash rate - so it's not really a negative thing in that respect - as long as the difficulty shares you are getting are appropriate for your hash rate.
See the posts by the BTC Statistics Squad for details about what difficulty shares are appropriate for your hash rate
(of course I am referring to people like organofcorti and Meni
) 
September 04, 2012, 02:32:13 PM
I'm really sorry for interrupting or asking such a dumb question, but I seemed to have missed whats the pro with the higher difficulty ?
Will I solve blocks faster ? Will I get paid more ? Will I have less stales ?!
Sorry & Thanks !
Will I solve blocks faster ? Will I get paid more ? Will I have less stales ?!
Sorry & Thanks !
I don't think it's a dumb question.
My understanding is that higher difficulty shares will take longer for a miner to mine. So a Difficulty 4 share would take your rig a approx 4 times as long to achieve so the pool will then pay 4 times the amount than it would for a diff 1 share.
So no you won't solve blocks faster, you won't get paid more and I don't know about stales.
The reason for this is for pools to prepare for the high hash power mining hardware that are coming out soonish. The higher difficulty shares require less bandwidth to and from the pool and less processing power at the pool end.
That's my understanding reading what different pool op's and Bitcoin experts have been posting here and there. I may be a little off, I usually am
.Sam
September 04, 2012, 02:28:26 PM
I've switched some of my workers to the variable diff server for testing
September 04, 2012, 01:49:37 PM
Less network and application overhead load for you.
A lot less network and application/execution overhead load for the pool.
A lot less network and application/execution overhead load for the pool.
September 04, 2012, 01:43:54 PM
I'm really sorry for interrupting or asking such a dumb question, but I seemed to have missed whats the pro with the higher difficulty ?
Will I solve blocks faster ? Will I get paid more ? Will I have less stales ?!
Sorry & Thanks !
Will I solve blocks faster ? Will I get paid more ? Will I have less stales ?!
Sorry & Thanks !
September 04, 2012, 01:40:33 PM
I think on average there should be 1 share for 1 getwork at 1diff, but I'm sure someone can correct me if I am wrong.
Stoppots: The variable difficulty is for every miner of every speed, that's the beauty of it. If you are less than about 500 MH/s, you'll get 1diff shares almost exclusively just like the current servers, but if you're > 500 MH/s, your difficulty will start going up according to how fast you are.
Stoppots: The variable difficulty is for every miner of every speed, that's the beauty of it. If you are less than about 500 MH/s, you'll get 1diff shares almost exclusively just like the current servers, but if you're > 500 MH/s, your difficulty will start going up according to how fast you are.
September 04, 2012, 12:37:27 PM
Not sure if it's a problem, it looks strange though. Connected to the var. diff. server.
I get the "New block detected on network before longpoll" message like 10-20 times, every time it shows up. Anyone else? Using CGminer 2.6.6 (Higher versions make my gpu crash and can't recover).
I get the "New block detected on network before longpoll" message like 10-20 times, every time it shows up. Anyone else? Using CGminer 2.6.6 (Higher versions make my gpu crash and can't recover).
September 04, 2012, 12:13:58 PM
Hi Graet, perhaps I am being overly observant watching out for conspiracies again.
Just because you ain't paranoid doesn't mean they aren't out to get you!
Sam
September 04, 2012, 11:17:42 AM
Hi Graet, perhaps I am being overly observant watching out for conspiracies again.
September 04, 2012, 11:04:48 AM
When did the change to no longer sticky the top 10 pools in the pools section occur?
Bitcoin Forum > Bitcoin > Mining > Pools
Seems like less than a week ago they were still stickied. Am I safe in assuming this is directly related to EMC's growing popularity and the soon to be added Variable Difficulty Shares(or similar shortened version) to EMC's subject title?
EDIT:
Decided to use the search feature and came across this thread.
https://bitcointalksearch.org/topic/top-10-pools-stickied-103313
yeah more likely diblo-d3 cant be bothered anymore, no-one responded to that thread or 2 similar in meta forum :/ Bitcoin Forum > Bitcoin > Mining > Pools
Seems like less than a week ago they were still stickied. Am I safe in assuming this is directly related to EMC's growing popularity and the soon to be added Variable Difficulty Shares(or similar shortened version) to EMC's subject title?
EDIT:
Decided to use the search feature and came across this thread.
https://bitcointalksearch.org/topic/top-10-pools-stickied-103313
Jump to: