Did you have your time for notifications set to a different number than it's set to now?
No change -- 30 min.
Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 163. (Read 499709 times)
December 28, 2011, 11:23:29 AM
No change -- 30 min.
December 28, 2011, 11:21:10 AM
Did you have your time for notifications set to a different number than it's set to now?
You can have the same worker on both ports. So long as the requested work gets submitted back to the same port, there should be no problems.
For your shares, it looks like they were queuing up in the prior block, I show 13607 submitted in that block, even though your accounting says 13394. Payouts are based on submitted and always have been. There's a slight disconnect between accounting and submitted due to timing issues between when a block is solved and how long it takes to process, so shares get credited (usually) to the prior block for block stat accounting while the block is processing if the iteration hasn't reached your workers yet, even though the getwork server is crediting the submitted shares to the "current" block.
I actually have a method 90% in place to speed up block processing so it's almost instant, I just haven't turned it on yet. If/when we move to PSJ, it will also virtually eliminate this issue as well. In either case, it's purely a display issue (as you can see from your payment being the same as your previous one), and I'll probably send something to comb the DB and recount all shares according to the submitted shares table instead of the user accounting table once the underlying issue is resolved.
You can have the same worker on both ports. So long as the requested work gets submitted back to the same port, there should be no problems.
For your shares, it looks like they were queuing up in the prior block, I show 13607 submitted in that block, even though your accounting says 13394. Payouts are based on submitted and always have been. There's a slight disconnect between accounting and submitted due to timing issues between when a block is solved and how long it takes to process, so shares get credited (usually) to the prior block for block stat accounting while the block is processing if the iteration hasn't reached your workers yet, even though the getwork server is crediting the submitted shares to the "current" block.
I actually have a method 90% in place to speed up block processing so it's almost instant, I just haven't turned it on yet. If/when we move to PSJ, it will also virtually eliminate this issue as well. In either case, it's purely a display issue (as you can see from your payment being the same as your previous one), and I'll probably send something to comb the DB and recount all shares according to the submitted shares table instead of the user accounting table once the underlying issue is resolved.
December 28, 2011, 11:16:11 AM
I opened another instance of the getwork server on port 9009. If some of you want to switch over to that port, that would be great. We aren't having any problems at the moment, but I would like to head off any potential problems before they become an issue.
So instead of connecting to port 8337, just use port 9009 and maybe set port 8337 as a backup.
So instead of connecting to port 8337, just use port 9009 and maybe set port 8337 as a backup.
Can I have the same worker on both ports or must they be different? Currently I have two different workers, with one on 8337 as failover backup as suggested. Occasionally a very few shares are submitted to the backup. To neaten my Workers list I'd prefer to remove the second worker.
December 28, 2011, 11:05:43 AM
Proofer - what hashrate are you mining at? It's possible you did not submit a share in that 8 minutes if your hashrate is lower.
During the interval in question, 2011-12-16 22:14:35 ... 22:22:33 inclusive PST my miner reported 205 shares accepted.
Quote
...
At any rate, I spent most of Monday working on PSJ with little to show for it. I remembered why I dislike OOP so much... 3x more coding for the same result as non-OOP. Sure, non-OOP is less maintainable or modular, but come on. Jeez.
At any rate, I spent most of Monday working on PSJ with little to show for it. I remembered why I dislike OOP so much... 3x more coding for the same result as non-OOP. Sure, non-OOP is less maintainable or modular, but come on. Jeez.
When I was a youngster like you and was doing mostly system software, I had the same reaction.[/condescension]
December 28, 2011, 10:43:44 AM
Subject: bogus worker-failed email alert
I logged in to the web site to look at my Block Stats pursuant to absorbing Inaba's recent reply to my inquiry on that subject, and then got this email:
But there was no discontinuity in the miner's generation of accepted shares:
In sum, the reported last activity was within one second of the generation of the email. Whether my logging in to the web site was cause or coincidence I don't know. And yes, pool 0 is indeed...
0: http://us.eclipsemc.com:9009
I logged in to the web site to look at my Block Stats pursuant to absorbing Inaba's recent reply to my inquiry on that subject, and then got this email:
Quote
...
from eclipse.communityhosting.net (eclipsemc.com. [69.30.224.137]) by mx.google.com with ESMTPS id wv5si23522212igb.62.2011.12.28.07.22.03 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Dec 2011 07:22:03 -0800 (PST)
...
(from josh@localhost) by eclipsemc.com (8.14.4/8.14.4/Submit) id pBSFM2RQ031809; Wed, 28 Dec 2011 09:22:02 -0600
...
You have asked to be notified when your miner, [...] has failed.
Our helper monkeys have determined that it has, in fact, failed.
The last activity we recieved on the miner was 2011-12-28 07:22:02
(America/Los_Angeles) . You may want to check on it.
from eclipse.communityhosting.net (eclipsemc.com. [69.30.224.137]) by mx.google.com with ESMTPS id wv5si23522212igb.62.2011.12.28.07.22.03 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Dec 2011 07:22:03 -0800 (PST)
...
(from josh@localhost) by eclipsemc.com (8.14.4/8.14.4/Submit) id pBSFM2RQ031809; Wed, 28 Dec 2011 09:22:02 -0600
...
You have asked to be notified when your miner, [...] has failed.
Our helper monkeys have determined that it has, in fact, failed.
The last activity we recieved on the miner was 2011-12-28 07:22:02
(America/Los_Angeles) . You may want to check on it.
But there was no discontinuity in the miner's generation of accepted shares:
Code:
[2011-12-28 07:21:48] Accepted 00000000.c9372a9c.e31b4ab2 GPU 4 thread 4 pool 0
[2011-12-28 07:21:48] Accepted 00000000.a8a042f4.85540439 GPU 1 thread 7 pool 0
[2011-12-28 07:21:56] Accepted 00000000.0b1eb6e6.197c2194 GPU 1 thread 7 pool 0
[2011-12-28 07:21:57] Accepted 00000000.40ad4052.00e0b4f1 GPU 3 thread 3 pool 0
[2011-12-28 07:21:57] Accepted 00000000.c383a550.cd88d5f8 GPU 2 thread 8 pool 0
[2011-12-28 07:21:58] Accepted 00000000.304646bf.32bd160e GPU 0 thread 6 pool 0
[2011-12-28 07:21:59] Accepted 00000000.982321f7.b91d4d55 GPU 5 thread 5 pool 0
[2011-12-28 07:22:01] Accepted 00000000.2df1b93a.c7de19e0 GPU 5 thread 11 pool 0
[2011-12-28 07:22:03] Accepted 00000000.27a0a503.539d1ac7 GPU 0 thread 6 pool 0
[2011-12-28 07:22:05] Accepted 00000000.12baec39.dd733aba GPU 1 thread 7 pool 0
[2011-12-28 07:22:05] Accepted 00000000.d46c4c4e.b18bb41d GPU 0 thread 0 pool 0
[2011-12-28 07:22:07] Accepted 00000000.73bc80d3.e8803b38 GPU 3 thread 9 pool 0
[2011-12-28 07:22:10] Accepted 00000000.6ab6eba1.4d54d075 GPU 5 thread 5 pool 0
[2011-12-28 07:22:12] Accepted 00000000.58cf492b.8b200027 GPU 1 thread 7 pool 0
[2011-12-28 07:22:13] Accepted 00000000.bf168b03.bb8323a1 GPU 1 thread 7 pool 0
[2011-12-28 07:22:22] Rejected 00000000.45a15d96.6e147cbf GPU 5 thread 5 pool 0
[2011-12-28 07:22:22] LONGPOLL detected new block on network, waiting on fresh work
[2011-12-28 07:22:23] Accepted 00000000.7fed39e4.1c5411e6 GPU 1 thread 1 pool 0
[2011-12-28 07:22:23] Accepted 00000000.28db40eb.4fe1611e GPU 4 thread 4 pool 0
[2011-12-28 07:22:23] Accepted 00000000.ba601325.ccc72654 GPU 4 thread 10 pool 0
[2011-12-28 07:22:24] Accepted 00000000.ba5991a3.c85052bb GPU 2 thread 2 pool 0
[2011-12-28 07:22:26] Accepted 00000000.606c0857.05bba2ff GPU 4 thread 10 pool 0
[2011-12-28 07:22:27] Accepted 00000000.369014c0.7147f0ef GPU 2 thread 8 pool 0
[2011-12-28 07:22:28] Accepted 00000000.ba30b50f.9ae5307e GPU 5 thread 11 pool 0
[2011-12-28 07:22:29] Accepted 00000000.5b2c683c.90633ea6 GPU 4 thread 4 pool 0
[2011-12-28 07:22:30] Accepted 00000000.740fe681.617e60b6 GPU 3 thread 3 pool 0
[2011-12-28 07:22:35] Accepted 00000000.f8d5b941.3cbee758 GPU 1 thread 7 pool 0
[2011-12-28 07:22:36] Accepted 00000000.71bb2bd3.7526cdb7 GPU 4 thread 10 pool 0
[2011-12-28 07:22:39] Accepted 00000000.8db2fea5.08d1ce50 GPU 2 thread 2 pool 0
[2011-12-28 07:22:39] Accepted 00000000.babae97a.8035c4c7 GPU 2 thread 2 pool 0
[2011-12-28 07:22:41] Accepted 00000000.5c69a779.15af7271 GPU 1 thread 7 pool 0
[2011-12-28 07:22:44] Accepted 00000000.c931eb7a.7f78380e GPU 1 thread 7 pool 0
[2011-12-28 07:22:44] Accepted 00000000.0f77f11f.4511b673 GPU 0 thread 6 pool 0
[2011-12-28 07:22:45] Accepted 00000000.7172649d.6f74014b GPU 1 thread 1 pool 0
[2011-12-28 07:22:50] Accepted 00000000.802caedc.fb80b273 GPU 3 thread 3 pool 0
[2011-12-28 07:22:52] Accepted 00000000.9b5168bc.2370abc0 GPU 0 thread 6 pool 0
[2011-12-28 07:22:57] Accepted 00000000.4c63550b.ead6a8a0 GPU 3 thread 3 pool 0
[2011-12-28 07:22:58] Accepted 00000000.112ee5fe.0f513d7c GPU 2 thread 8 pool 0
[2011-12-28 07:22:59] Accepted 00000000.2bbe04fd.6bad2729 GPU 4 thread 4 pool 0
[2011-12-28 07:22:59] Accepted 00000000.ac0a96cf.32701168 GPU 2 thread 2 pool 0
[2011-12-28 07:23:02] Accepted 00000000.64dee0e3.547d2334 GPU 0 thread 6 pool 0
[2011-12-28 07:23:05] Accepted 00000000.cb96829b.5efe6346 GPU 0 thread 6 pool 0
[2011-12-28 07:21:48] Accepted 00000000.a8a042f4.85540439 GPU 1 thread 7 pool 0
[2011-12-28 07:21:56] Accepted 00000000.0b1eb6e6.197c2194 GPU 1 thread 7 pool 0
[2011-12-28 07:21:57] Accepted 00000000.40ad4052.00e0b4f1 GPU 3 thread 3 pool 0
[2011-12-28 07:21:57] Accepted 00000000.c383a550.cd88d5f8 GPU 2 thread 8 pool 0
[2011-12-28 07:21:58] Accepted 00000000.304646bf.32bd160e GPU 0 thread 6 pool 0
[2011-12-28 07:21:59] Accepted 00000000.982321f7.b91d4d55 GPU 5 thread 5 pool 0
[2011-12-28 07:22:01] Accepted 00000000.2df1b93a.c7de19e0 GPU 5 thread 11 pool 0
[2011-12-28 07:22:03] Accepted 00000000.27a0a503.539d1ac7 GPU 0 thread 6 pool 0
[2011-12-28 07:22:05] Accepted 00000000.12baec39.dd733aba GPU 1 thread 7 pool 0
[2011-12-28 07:22:05] Accepted 00000000.d46c4c4e.b18bb41d GPU 0 thread 0 pool 0
[2011-12-28 07:22:07] Accepted 00000000.73bc80d3.e8803b38 GPU 3 thread 9 pool 0
[2011-12-28 07:22:10] Accepted 00000000.6ab6eba1.4d54d075 GPU 5 thread 5 pool 0
[2011-12-28 07:22:12] Accepted 00000000.58cf492b.8b200027 GPU 1 thread 7 pool 0
[2011-12-28 07:22:13] Accepted 00000000.bf168b03.bb8323a1 GPU 1 thread 7 pool 0
[2011-12-28 07:22:22] Rejected 00000000.45a15d96.6e147cbf GPU 5 thread 5 pool 0
[2011-12-28 07:22:22] LONGPOLL detected new block on network, waiting on fresh work
[2011-12-28 07:22:23] Accepted 00000000.7fed39e4.1c5411e6 GPU 1 thread 1 pool 0
[2011-12-28 07:22:23] Accepted 00000000.28db40eb.4fe1611e GPU 4 thread 4 pool 0
[2011-12-28 07:22:23] Accepted 00000000.ba601325.ccc72654 GPU 4 thread 10 pool 0
[2011-12-28 07:22:24] Accepted 00000000.ba5991a3.c85052bb GPU 2 thread 2 pool 0
[2011-12-28 07:22:26] Accepted 00000000.606c0857.05bba2ff GPU 4 thread 10 pool 0
[2011-12-28 07:22:27] Accepted 00000000.369014c0.7147f0ef GPU 2 thread 8 pool 0
[2011-12-28 07:22:28] Accepted 00000000.ba30b50f.9ae5307e GPU 5 thread 11 pool 0
[2011-12-28 07:22:29] Accepted 00000000.5b2c683c.90633ea6 GPU 4 thread 4 pool 0
[2011-12-28 07:22:30] Accepted 00000000.740fe681.617e60b6 GPU 3 thread 3 pool 0
[2011-12-28 07:22:35] Accepted 00000000.f8d5b941.3cbee758 GPU 1 thread 7 pool 0
[2011-12-28 07:22:36] Accepted 00000000.71bb2bd3.7526cdb7 GPU 4 thread 10 pool 0
[2011-12-28 07:22:39] Accepted 00000000.8db2fea5.08d1ce50 GPU 2 thread 2 pool 0
[2011-12-28 07:22:39] Accepted 00000000.babae97a.8035c4c7 GPU 2 thread 2 pool 0
[2011-12-28 07:22:41] Accepted 00000000.5c69a779.15af7271 GPU 1 thread 7 pool 0
[2011-12-28 07:22:44] Accepted 00000000.c931eb7a.7f78380e GPU 1 thread 7 pool 0
[2011-12-28 07:22:44] Accepted 00000000.0f77f11f.4511b673 GPU 0 thread 6 pool 0
[2011-12-28 07:22:45] Accepted 00000000.7172649d.6f74014b GPU 1 thread 1 pool 0
[2011-12-28 07:22:50] Accepted 00000000.802caedc.fb80b273 GPU 3 thread 3 pool 0
[2011-12-28 07:22:52] Accepted 00000000.9b5168bc.2370abc0 GPU 0 thread 6 pool 0
[2011-12-28 07:22:57] Accepted 00000000.4c63550b.ead6a8a0 GPU 3 thread 3 pool 0
[2011-12-28 07:22:58] Accepted 00000000.112ee5fe.0f513d7c GPU 2 thread 8 pool 0
[2011-12-28 07:22:59] Accepted 00000000.2bbe04fd.6bad2729 GPU 4 thread 4 pool 0
[2011-12-28 07:22:59] Accepted 00000000.ac0a96cf.32701168 GPU 2 thread 2 pool 0
[2011-12-28 07:23:02] Accepted 00000000.64dee0e3.547d2334 GPU 0 thread 6 pool 0
[2011-12-28 07:23:05] Accepted 00000000.cb96829b.5efe6346 GPU 0 thread 6 pool 0
In sum, the reported last activity was within one second of the generation of the email. Whether my logging in to the web site was cause or coincidence I don't know. And yes, pool 0 is indeed...
0: http://us.eclipsemc.com:9009
December 28, 2011, 10:08:59 AM
Sorting is working... YAH! Thank you sir.
edit:
this one pops to the top on every metric.
(power set at 1250W)
jjiimm_64_miner11 3.24 GH/s 970 5699 598202 1 s ฿ 2.07 ($8.42) / day
being able to sort 15 miners to see which ones are most profitable at any given time is very handy.. Thanks again. I have doubled my donation for the month of Jan
edit:
this one pops to the top on every metric.
(power set at 1250W)jjiimm_64_miner11 3.24 GH/s 970 5699 598202 1 s ฿ 2.07 ($8.42) / day
being able to sort 15 miners to see which ones are most profitable at any given time is very handy.. Thanks again. I have doubled my donation for the month of Jan
December 28, 2011, 09:18:43 AM
So to answer the questions:
Proofer - what hashrate are you mining at? It's possible you did not submit a share in that 8 minutes if your hashrate is lower.
For prop differential, it shows you how much you earned compared to a completely fair, unhopped proportional distribution. It's kind of a misleading stat in so far as you can't view just one block and look at the prop differential, you have to take about 7 blocks before and 7 blocks after a given block to get a good idea of your true differential (which should approach 0%)... there is about a 5 block lag time between when you see changes to your differential and something significant happening that would change your differential...
Your earning (and donation) in that row, even if your shares submitted is 0, is due to DGM paying you for work done on other blocks. Because of the way block changes are handled in the background, some shares for a given block may be submitted to the share before or after the given block... it's entirely possible if you only submitted a few shares in 8 minutes that those shares were attributed to the block prior or the block after - in either case you're still credited for the block, though, instead of them being discarded, like most pools.
At any rate, I spent most of Monday working on PSJ with little to show for it. I remembered why I dislike OOP so much... 3x more coding for the same result as non-OOP. Sure, non-OOP is less maintainable or modular, but come on. Jeez.
I'm going to turn my attention to other things for a bit and come back to PSJ this weekend. If anyone is a crack Java programmer that wants to make some mods to PSJ, I'd be interested in hearing from you. I'd really like to make the mods I need be pluggable, but after working on it, I'm having trouble envisioning how it might get done with the PSJ pluggable engine without modifying the source.
Proofer - what hashrate are you mining at? It's possible you did not submit a share in that 8 minutes if your hashrate is lower.
For prop differential, it shows you how much you earned compared to a completely fair, unhopped proportional distribution. It's kind of a misleading stat in so far as you can't view just one block and look at the prop differential, you have to take about 7 blocks before and 7 blocks after a given block to get a good idea of your true differential (which should approach 0%)... there is about a 5 block lag time between when you see changes to your differential and something significant happening that would change your differential...
Your earning (and donation) in that row, even if your shares submitted is 0, is due to DGM paying you for work done on other blocks. Because of the way block changes are handled in the background, some shares for a given block may be submitted to the share before or after the given block... it's entirely possible if you only submitted a few shares in 8 minutes that those shares were attributed to the block prior or the block after - in either case you're still credited for the block, though, instead of them being discarded, like most pools.
At any rate, I spent most of Monday working on PSJ with little to show for it. I remembered why I dislike OOP so much... 3x more coding for the same result as non-OOP. Sure, non-OOP is less maintainable or modular, but come on. Jeez.
I'm going to turn my attention to other things for a bit and come back to PSJ this weekend. If anyone is a crack Java programmer that wants to make some mods to PSJ, I'd be interested in hearing from you. I'd really like to make the mods I need be pluggable, but after working on it, I'm having trouble envisioning how it might get done with the PSJ pluggable engine without modifying the source.
December 27, 2011, 02:00:00 PM
I don't know too much either, but I believe this is due to the double geometric method. You don't earn as much right away, but as you continue to mine, you get up to your expected earnings.
I'll let Inaba or someone else with more knowledge give you a true detailed explanation, but it has something to do with what I posted.
I'll let Inaba or someone else with more knowledge give you a true detailed explanation, but it has something to do with what I posted.
December 27, 2011, 01:53:03 PM
Brutal 24 hour+ round, but I broke my cherry and found us a block 8 minutes later!
...
...
This is a technical question from a newbie, not a complaint or whine...
In the My Shares column of Block Stats, in the row for jjshabadoo's block it shows 0, although I was mining continuously during that 8-minute period. Why 0? Meanwhile, My Earning (what does Prop Diff denote?) and Donation in that row are positive.
December 27, 2011, 01:29:08 PM
Brutal 24 hour+ round, but I broke my cherry and found us a block 8 minutes later!
My first block found in any pool. I think getting up to 5+ GHash helped. I have enough cards and gear to get up to almost 12 GHash soon. I'm hoping to get them all running by january 4th because I'm having surgery that day.
Great pool so far and I hope to keep contributing for a long time.
My first block found in any pool. I think getting up to 5+ GHash helped. I have enough cards and gear to get up to almost 12 GHash soon. I'm hoping to get them all running by january 4th because I'm having surgery that day.
Great pool so far and I hope to keep contributing for a long time.
December 27, 2011, 04:33:02 AM
Oh great, as soon as the horrible unluck cycle ended, one of my rigs melted. This pool is possessed I tell you 
December 26, 2011, 08:06:57 PM
Well, the hashrate keeps climbing! Remember, port 9009 is available for connections as well as 8337!
Anyway, I will be working on stuff this week, including being able to sort your miners as well as poolserverj. I may just go ahead and modify the source directly, at least until Shads gets back to me (maybe he's on vacation?) about some things I need in PSJ to accomodate DGM in the fashion I have it implemented.
Hope everyone had a good Christmas. I'm still trying to dig my way out of it!
Anyway, I will be working on stuff this week, including being able to sort your miners as well as poolserverj. I may just go ahead and modify the source directly, at least until Shads gets back to me (maybe he's on vacation?) about some things I need in PSJ to accomodate DGM in the fashion I have it implemented.
Hope everyone had a good Christmas. I'm still trying to dig my way out of it!
Sweet, will be glad to see the sorting.
On another note, i finally read thru all the posts about the 80Watt small miner you've been testing. Don't want to put the name here for fear of the thread getting hijacked
. I am really looking forward to see how that pans out.I will raise my donation now. maybe that will spur the bitcoin gods to give us a break on these multi million share blocks.
December 26, 2011, 02:17:08 PM
Well, the hashrate keeps climbing! Remember, port 9009 is available for connections as well as 8337!
Anyway, I will be working on stuff this week, including being able to sort your miners as well as poolserverj. I may just go ahead and modify the source directly, at least until Shads gets back to me (maybe he's on vacation?) about some things I need in PSJ to accomodate DGM in the fashion I have it implemented.
Hope everyone had a good Christmas. I'm still trying to dig my way out of it!
Anyway, I will be working on stuff this week, including being able to sort your miners as well as poolserverj. I may just go ahead and modify the source directly, at least until Shads gets back to me (maybe he's on vacation?) about some things I need in PSJ to accomodate DGM in the fashion I have it implemented.
Hope everyone had a good Christmas. I'm still trying to dig my way out of it!
December 25, 2011, 08:03:32 PM
Inaba,
I know your very busy. and you have been more then helpful with pool enhancements and bug fixes.. thank you.
I have a request, instead of the tool tips setting/removal (i know that is a pita) can you PLEASE make the columns on the worker page sortable. I would love to be able to see which rigs are most profitable by sorting the profit column, or the reseted shares column.
as an incentive, I will double my donation for a month
thxs for a great pool!
Jim
December 25, 2011, 04:38:16 PM
Current Speed 303.83 GH/s!!! AWESOME GUYS!!!
Best pool ever!!
Best pool ever!!
December 25, 2011, 01:57:06 PM
Inaba,
I know your very busy. and you have been more then helpful with pool enhancements and bug fixes.. thank you.
I have a request, instead of the tool tips setting/removal (i know that is a pita) can you PLEASE make the columns on the worker page sortable. I would love to be able to see which rigs are most profitable by sorting the profit column, or the reseted shares column.
as an incentive, I will double my donation for a month
thxs for a great pool!
Jim
December 25, 2011, 06:01:31 AM
I think our highest round is a 6.x million round. I hope we never break that record.
6.x is low.You will break that sooner or later.
Edit: also, quoting shares is rather meaningless.
The number that is relevant is the ratio of shares to difficulty.
So 6.5 is currently 563% - which isn't any where near some of the large pool records.
Edit2: quick recent check: deepbit block "18.12 10:01:04" 4h 21m 10,489,615 - which is 908%
the ratio of shares to difficulty is a good measure,
it contains the impact of difficulty, a stat for the ratio is better than shares
December 24, 2011, 11:33:57 PM
Brought my 2GH to your pool Might as well! You guys have everything and then some!
Might as well! You guys have everything and then some! 
December 23, 2011, 07:33:07 PM
I think our highest round is a 6.x million round. I hope we never break that record.
6.x is low.You will break that sooner or later.
Edit: also, quoting shares is rather meaningless.
The number that is relevant is the ratio of shares to difficulty.
So 6.5 is currently 563% - which isn't any where near some of the large pool records.
Edit2: quick recent check: deepbit block "18.12 10:01:04" 4h 21m 10,489,615 - which is 908%
December 23, 2011, 01:46:24 PM
I think our highest round is a 6.x million round. I hope we never break that record.
Jump to: