I know variance is a...err... "pain" and all, but heavens to betsy! is this the worst luck ever.A 5:42 round, followed directly by a 6:56 round which *still* hasn't ended!!!And this isn't some small pool with 400 GH/s. We've collectively thrown 1200 GH/s at this for hours and still can't get a block -- I notice the number is dropping, as people give up.

Um, no. I cut off ~100GHash by moving webserver (mining.bitcoin.cz) from London to France, then I realized a lot of people has been mining on this URL and setup HTTP proxy here, so this hashrate is back. Unfortunately miners using URL mining.bitcoin.cz are routed thru France server, so their mining experience may be a little... crappy.

Except this issue there wasn't any downtime on pool today, so those two long rounds are just really bad luck. There's no reason to think that anything is wrong, I'm keeping my eyes on pool all day.

Um, no. I cut off ~100GHash by moving webserver (mining.bitcoin.cz) from London to France, then I realized a lot of people has been mining on this URL and setup HTTP proxy here, so this hashrate is back. Unfortunately miners using URL mining.bitcoin.cz are routed thru France server, so their mining experience may be a little... crappy.

Except this issue there wasn't any downtime on pool today, so those two long rounds are just really bad luck. There's no reason to think that anything is wrong, I'm keeping my eyes on pool all day.

So if my physical location is London which is the best URL or IP to be using ( api or api2 or something else ) ? It seems ATM I am not supposed to use an IP or mining.bitcoin.cz right ?

* Website is working in France very well* There wasn't any issue on mining (if you're using correct URLs)* The rest (database server, mining backends) are prepared for migration, I'll continue tomorrow.

So if my physical location is London which is the best URL or IP to be using ( api or api2 or something else ) ? It seems ATM I am not supposed to use an IP or mining.bitcoin.cz right ?

It does not matter, both (api and api2) will point to France since tomorrow. But mining.bitcoin.cz won't be working since tomorrow anymore, I just setup routing thru webserver, which is dirty hack which is only giving time to users to fix their settings.

Btw latency between both servers is under 4ms, so if you're in London, the migration should not affect you at all - connection to France is excellent.

What's your miner? Is it doing better on api.bitcoin.cz? Actually mining over webserver could be a reason for additional latency, because webserver was pretty overloaded (all those mining widgets polling webserver every minute are making me mad). And because webserver was doing only a proxy for your requests, I didn't see this latency in backend log.

I know variance is a...err... "pain" and all, but heavens to betsy! is this the worst luck ever.A 5:42 round, followed directly by a 6:56 round which *still* hasn't ended!!!And this isn't some small pool with 400 GH/s. We've collectively thrown 1200 GH/s at this for hours and still can't get a block -- I notice the number is dropping, as people give up.

What's your miner? Is it doing better on api.bitcoin.cz? Actually mining over webserver could be a reason for additional latency, because webserver was pretty overloaded (all those mining widgets polling webserver every minute are making me mad). And because webserver was doing only a proxy for your requests, I didn't see this latency in backend log.

It's absolutely fine now, I'm partly to blame myself since I have a widget running in chrome

Thanks !!!

It will be a juicy namecoin payout for this block ! Already 50 NMC blocks have been found in this 10 hour period... running bad on one side and lucky on the other... I love merged mining

Damn, so that magic "bug" is solved. Many users were complaining for pool performance and "magical network issues" (mainly GUIminers, now I understand why!). And it was because they were using bad URL and mining thru webserver. I setup this transparent proxy 6 months ago right because GUIminer's hardcoded old URL, but then I completely forgot to it. And I was unable to link people's mining issues with webserver load, LOL.

Say you have a 24 hour round (purely hypothetical!) and my miners are with you for the first 12 hours, then I switch to another pool.My BTC reward will dwindle to almost nothing; that much I understand.

But what about the Namecoin blocks? Say you find 50 the first 12 hours, and 50 the second 12 hours. Would I get my usual share of the first 50 (the time I was contributing fully), and then next to nothing (or actual nothing) of the "second" 50 NMC blocks?

In other words, are NMC blocks divided up based on the shares for that NMC block, or is some other algorithm used? I guess I'm asking if NMC and BTC division are separate.

I would hope so, otherwise anyone hearing that 50 NMC blocks were found on Slush would hurry up and join the round, and contribute full shares for 5 or 10 minutes, to get a huge payday!

It's looking like my guess was incorrect -- it looks like you calculate ALL the NMC blocks proportionate to the last BTC round.

So if you get a long round (like the last one -- 12:58) and word gets out that there's a nice NMC jackpot, everyone's going to want to join for that last 30 minutes so they can get a massive NMC payday.

That's ridiculous if you ask me.

I, for example, was with your pool 100% for the first 7 HOURS or so of the round -- I should get my usual share of NMC blocks found during that period.

The only problem with what you're saying above is that no one really knows when a block is going to end. Reverse hopping is only theoretically possible as no one really knows how long the block will be