Quick question from a newbie:  is there a general consensus on the hashrate where proportional is more profitable than PPS (or vice versa) over the long-term?

I've had alot of those "none"s too

No, I think that there was "None" just because the round was only few seconds long.

I don't see anything wrong with you at my side, it's strange. May be you had some connection problems.

This may correspond to the following "None" (I notice a few today).

Time/Link                      Found in   Total shares   Reward
04.05.2011 17:45:57      0h 08m    38530      0.05412665
04.05.2011 17:37:18      1h 15m    343831      0.05007547
04.05.2011 16:22:11      0h 00m    625         None
04.05.2011 16:22:00      0h 29m    134977      0.05138283

Sent.

Looks fine to me.
PM me your login, i'll check my logs.

Non-authoritative answer:
Name:    deepbit.net
Address:  46.4.99.204

telnet makes a connection, but no text response.  I hit ctrl-c to break the connection and get:

 

400 Bad Request

---

nginx/1.0.0




Connection to host lost.

Traceroute shows a convoluted route through what looks like France and Germany.

Tracing route to deepbit.net [46.4.99.204]
over a maximum of 30 hops:

  1     7 ms     6 ms     7 ms  73.115.174.1
  2     7 ms     7 ms     7 ms  ge-9-1-ur02.hamlake.mn.minn.comcast.net [68.85.165.229]
  3     8 ms     9 ms     *     te-0-3-0-2-ar01.roseville.mn.minn.comcast.net [68.87.174.70]
  4    19 ms    17 ms    18 ms  te-0-4-0-0-cr01.chicago.il.ibone.comcast.net [68.86.91.137]
  5    94 ms    53 ms    54 ms  pos-2-10-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.86.113]
  6    54 ms    53 ms    53 ms  pos-0-4-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.85.22]
  7    53 ms     *       53 ms  nyk-s2-rou-1001.us.eurorings.net [75.149.228.126]
  8    82 ms    53 ms    53 ms  nyk-s2-rou-1021.US.eurorings.net [134.222.226.38]
  9   157 ms   149 ms   133 ms  nntr-s1-rou-1022.FR.eurorings.net [134.222.226.162]
 10   143 ms   141 ms   141 ms  ffm-s1-rou-1022.DE.eurorings.net [134.222.229.30]
 11     *      141 ms   189 ms  ffm-s1-rou-1021.DE.eurorings.net [134.222.231.141]
 12   147 ms   145 ms   145 ms  nbg-s1-rou-1001.DE.eurorings.net [134.222.225.26]
 13   145 ms   147 ms   146 ms  kpn-gw.hetzner.de [134.222.107.21]
 14   163 ms   150 ms   160 ms  hos-bb2.juniper1.fs.hetzner.de [213.239.240.146]
 15   148 ms   151 ms   174 ms  hos-tr1.ex3k7.rz14.hetzner.de [213.239.224.136]
 16     *      149 ms   152 ms  j2.deepbit.net [46.4.99.204]

Trace complete.

Also, the idle warnings are still occurring.

Open your command prompt and try the following commands:

nslookup deepbit.net

And

telnet deepbit.net 8332

Tell me what outputs do you get.
Also you'd better send that long log to my PM, not here :)

Set your averaging window to 30 minutes in advanced settings and try again - then luck meter will be more precise. Short drops or peaks are absolutely normal because sometimes you are more lucky and sometimes not.

Here is a list starting when I first started seeing it.  Note this is long ...

Listener for "Deepbit": 04/05/2011 13:03:34, long poll: new block 000035eb555f7109
Listener for "Deepbit": 04/05/2011 13:16:05, long poll: new block 00000783c8fcd3c4
Listener for "Deepbit": 04/05/2011 13:17:53, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 13:17:53, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 13:18:09, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 13:18:10, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 13:18:18, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 13:18:32, long poll: new block 000012af4599a6e0
Listener for "Deepbit": 04/05/2011 13:19:23, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 13:19:23, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 13:19:33, long poll: new block 000056dd26cf24b3
Listener for "Deepbit": 04/05/2011 13:26:33, long poll: new block 000026ffb9405747
Listener for "Deepbit": 04/05/2011 13:35:30, long poll: new block 0000197f32cec885
Listener for "Deepbit": 04/05/2011 13:39:12, long poll: new block 0000141f10dd8139
Listener for "Deepbit": 04/05/2011 13:42:13, long poll: new block 00005863965ade33
Listener for "Deepbit": 04/05/2011 13:46:51, long poll: new block 000022695f4cbb69
Listener for "Deepbit": 04/05/2011 13:50:06, long poll: new block 00001aa30d88f230
Listener for "Deepbit": 04/05/2011 14:04:12, long poll: new block 000039f548f245f7
Listener for "Deepbit": 04/05/2011 14:05:45, long poll: new block 000008ded7e6be58
Listener for "Deepbit": 04/05/2011 14:44:16, long poll: new block 0000764562ab68c2
Listener for "Deepbit": 04/05/2011 14:47:11, long poll: new block 000023cfd11507d9
Listener for "Deepbit": 04/05/2011 14:57:00, long poll: new block 00005eb077fca76b
Listener for "Deepbit": 04/05/2011 15:12:13, long poll: new block 0000855b0b0af926
Listener for "Deepbit": 04/05/2011 15:14:59, long poll: new block 000061bc76e3466e
Listener for "Deepbit": 04/05/2011 15:17:39, long poll: new block 00006a2c9b40a8d1
Listener for "Deepbit": 04/05/2011 15:21:34, long poll: new block 00004a1accfc9fe4
Listener for "Deepbit": 04/05/2011 15:22:37, long poll: new block 00009368dccdd23c
Listener for "Deepbit": 04/05/2011 15:34:17, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 15:35:22, long poll: new block 000081a7f8408258
Listener for "Deepbit": 04/05/2011 15:46:16, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 15:46:16, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 15:50:03, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 15:50:03, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 15:51:45, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 15:51:46, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 15:52:47, long poll: new block 0000967a22b958bc
Listener for "Deepbit": 04/05/2011 15:54:32, long poll: new block 00000f5e7fb39e76
Listener for "Deepbit": 04/05/2011 16:00:41, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 16:00:42, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 16:05:25, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 16:09:38, long poll: new block 000068407a6768ab
Listener for "Deepbit": 04/05/2011 16:11:11, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 16:11:11, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 16:16:17, long poll: new block 00004c05f2ed4597
Listener for "Deepbit": 04/05/2011 16:17:56, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 16:22:00, long poll: new block 00007a7aa1116f24
Listener for "Deepbit": 04/05/2011 16:22:11, long poll: new block 000094f254e851f0
Listener for "Deepbit": 04/05/2011 16:24:32, long poll: new block 000070109bf8c695
Listener for "Deepbit": 04/05/2011 16:44:01, long poll: new block 00006d431e05f644
Listener for "Deepbit": 04/05/2011 16:45:17, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 16:46:57, long poll: new block 00007cfedffce7a2
Listener for "Deepbit": 04/05/2011 16:48:54, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 16:51:55, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 16:51:55, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 16:53:23, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 16:53:24, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 16:57:46, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 17:09:47, long poll: new block 000074f180ae5f0a
Listener for "Deepbit": 04/05/2011 17:10:34, long poll: new block 000001b34fa555da
Listener for "Deepbit": 04/05/2011 17:13:18, long poll: new block 0000151e507c76ad
Listener for "Deepbit": 04/05/2011 17:24:22, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 17:26:38, long poll: new block 00002f3427f02d18
Listener for "Deepbit": 04/05/2011 17:31:29, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 17:31:30, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 17:34:23, long poll: new block 000080247f9334f1
Listener for "Deepbit": 04/05/2011 17:37:18, long poll: new block 00000182fab8bdec
Listener for "Deepbit": 04/05/2011 17:43:35, long poll: new block 000026c251a79438
Listener for "Deepbit": 04/05/2011 17:45:57, long poll: new block 0000781183a2e1a9
Listener for "Deepbit": 04/05/2011 17:46:43, long poll: new block 00000b3542f08cdc
Listener for "Deepbit": 04/05/2011 17:48:40, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 17:48:47, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 17:56:44, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 17:58:09, long poll: new block 0000094d2c016d84
Listener for "Deepbit": 04/05/2011 17:58:59, long poll: new block 000066b8b1805c35

Thanks for the reply, im using the new windows GUI interface with a 6990, usage never drops through afterburner and hash rate (according to clint never wavers too much at all) is this a client problem? do I need to ask nicely for them to fix it? (Im doing Pay per share - which is why it matters)

GUIMiner v2011-04-26

Passing -v -w 128 -f 40 for my Radeon 6970.

Looking over the last 24 hours, this has happened several times.  VPN is stable, Netflix doesn't hiccup, connections elsewhere are very stable.  This appears to be outside of Comcast ... can't say whether it is your servers or network unless I can run diagnostics on it when it happens and if the "mini outage" is long enough to do so.

If you are using proportional mode - look at your history column for more realistic speed guesstimation.
Also you may be using phoenix miner, many users reported that it's internal hashrate meter may show higher values.

What miner do you use ?

I have noticed a lot of communication failures to the pool.  I see the hash rate drop suddenly [and my fan quiet down and a second later everything is back to normal.

Listener for "Deepbit": 04/05/2011 17:31:30, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 17:34:23, long poll: new block 000080247f9334f1
Listener for "Deepbit": 04/05/2011 17:37:18, long poll: new block 00000182fab8bdec
Listener for "Deepbit": 04/05/2011 17:43:35, long poll: new block 000026c251a79438
Listener for "Deepbit": 04/05/2011 17:45:57, long poll: new block 0000781183a2e1a9
Listener for "Deepbit": 04/05/2011 17:46:43, long poll: new block 00000b3542f08cdc
Listener for "Deepbit": 04/05/2011 17:48:40, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 17:48:47, Problems communicating with bitcoin RPC


I didn't have this problem using Slush or BTCMine, but there are reasons that I am using deepbit right now.

Tycho ... do you know what is going on?  BTW ... I have been using Google DNS for months (I figure nothing on the Internet is truly private these days, so at least the blame can all fall on one company ).

It just happened again less than a couple of minutes later ... note the overlap here for context.

Listener for "Deepbit": 04/05/2011 17:46:43, long poll: new block 00000b3542f08cdc
Listener for "Deepbit": 04/05/2011 17:48:40, warning: job finished, miner is idle
Listener for "Deepbit": 04/05/2011 17:48:47, Problems communicating with bitcoin RPC
Listener for "Deepbit": 04/05/2011 17:56:44, warning: job finished, miner is idle

Is there any explanation why i never go below 700 in my mining client, but frequently recently go too 500 mhash/s in the stats?

If you don't use the long polling, you can put unlimited number of miners on the same worker credentials. If your client supports long polling then I would recommend creating new worker account for each 10 miners (there is a trigger that suspects LP malfunction if you use more than 20 LP clients on one worker, but if you really need more - I can disable it by request).

Hey thanks for the tip! I dint notice that!

I would like to be able to rename workers too

I have a question though, do I put all my machines on the same worker, is this a bad thing? I'm rather curious if I should split them up...

does it matter? Or is it just a preference for you guys to keep track of each rig?

Seconding what Veldy said.  I'd love to see the Found Blocks actually associated with the workers similar to how slush shows it.  That way when I have to take my anger out on a rig I know which one has been slacking!

And any chance of being able to rename workers soon?

Similar thing happened to me.  With my NVidia 570GTX (~133MH/s at the time), I found two blocks in a short period of time on deepbit.  I have updated to a Radeon 6970 and haven't found one yet [in any pool] and it runs about 366MH/s currently.

BTW, if you go to your account and hit the advanced settings button, down under the BBCode textbox is a line that says how many blocks you have found historically.  Just a little tip.

Tycho - if you read this, I think that could be located a little more prominently in a better location if you get around to doing it.  Just a suggestion.  Thanks.