[1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration!

[village.idiot]

So the problem is with my ISP?

Okay I'll see if I can get them do do something.

Thanks

[1713887333]

1713887333

[1713887333]

1713887333

[JayCoin]

Just completed a webpage for charting hash rate of my miners.  I set it up so anyone can enter their API and chart their own hash rate. Is anyone interested?  If there is a lot of interest I would like to get Inaba to set up the api so I could grab multiple users data in one HTTPS call.

[freshzive]

Using BTCMon (iphone app), workers on EMC that are over 1Gh/s report an order of magnitude lower speed than they should. i.e. a worker (cgminer) doing 1.24Gh/s reports on the app 1.24Mh/s. I'm not sure if this is something to specific to how EMC reports with API or if it's the app itself misreading something. Anyway, if it is on EMC's side, is it possible for you to fix?

Thanks

[Inaba]

JayCoin: I will be happy to setup whatever makes it easier to aggregate the data, just let me know what you need specifically.

freshzive: I don't have an iPhone, so I'm not sure what it's doing (or not doing exactly) but I can change/add to the API to make it easier for applications like that to pull the data, I just need to know what is the best format to do.

Right now, the API returns the data in GH/s or MH/s by default depending on your speed.  However, you can disable this and only return MH/s or only return GH/s by adding either gh=Y or mh=Y do the end of the http GET call.  mh=Y will only return MH/s, so even if you have a 2 GH/s miner, it will read 2000 MH/s instead of 2 GH/s, the same goes for gh=Y, which will read .2 GH/s for a 200 MH/s miner. 

[stiftmaster]

On the Block Stats Page I see 59,72% luck
Clingman88    165904        14:51:47     01:41:56    711147        59.72%

when I click on Clingman88 stands there -48,45%
510    165904    2012-02-08 14:51:47    01:41:56    711147    -48.45%

What´s the different?

./stiftmaster

[Inaba]

Hmm, I need to update that page. It uses the old calculation of +/- % instead of 0 - 100% that the block stats page uses.  Basically they are the same number, just expressed in different ways. 

The blocks stats page is saying 59.72% of the blocks are longer than this one.

Your found blocks page is saying it is 48.45% under difficulty.

[GenTarkin]

Inaba, go kill more people in BF3, we need this 10hr block to solve!

[JayCoin]

Just completed a webpage for charting hash rate of my miners.  I set it up so anyone can enter their API and chart their own hash rate. Is anyone interested?  If there is a lot of interest I would like to get Inaba to set up the api so I could grab multiple users data in one HTTPS call.

Here is a link to my webpage for tracking your hashrate. I put my API here to show an example. More graphs and features will follow.

http://serason.com/projects/emccharts/?api=jaycoinapi&method=hashrate

[Inaba]

Very nice - what are you using to generate the charts?

[JayCoin]

Very nice - what are you using to generate the charts?

Thanks.

I am using the Flot plugin for Jquery.

I was thinking that you could set up an api where I can send a request with POST data in a variable called 'bulk_users'.  The data would be JSON encoded as follows.

{"users":[{"api":"user1api","action":"userstats"},{"api":"user2api","action":"userstats"},{"api":"user3api","action":"userstats"}]}

would that work?

[village.idiot]

So it looks like the problem is here: 68.85.38.86

I'm not sure who owns that, probably comcast, but it appears that router has some weird routing loop going on when connecting to 208.110.68.0/24. 

Comcast said they had to turn off something to do with smart packets.

Now I'm back to mining and it's good to be getting some warmth from my rig under my bench.

[cyberlync]

I'm still having issues with server communication. It seems that whenever we solve a block, I cannot communicate with the servers for a few minutes, tried all the servers, us1/2/3, tried various miners, kernels and internet connections. While it's not a problem for the most part, there is the problem when we solve a fast block, it can be very possible for me not to be able to submit any shares. My connection works fine for everything else, so I think it might be something to do with me connecting to the US servers from Europe, and when we solve a block, and new work has to be distributed, the fact that I'm in Europe, might be reason why I can't come through the "congested" route. At least that is my idea, been watching it happen every single time we solve a block now, this did not occur at my previous pool (MMC).

[GenTarkin]

I'm still having issues with server communication. It seems that whenever we solve a block, I cannot communicate with the servers for a few minutes, tried all the servers, us1/2/3, tried various miners, kernels and internet connections. While it's not a problem for the most part, there is the problem when we solve a fast block, it can be very possible for me not to be able to submit any shares. My connection works fine for everything else, so I think it might be something to do with me connecting to the US servers from Europe, and when we solve a block, and new work has to be distributed, the fact that I'm in Europe, might be reason why I can't come through the "congested" route. At least that is my idea, been watching it happen every single time we solve a block now, this did not occur at my previous pool (MMC).

Yeah, Ive seen this issue w/ EMC for a while, its like the pool lags out a bit when it solves a block. Thats the only time I get really high stales is after EMC actually solves the block.
Im in the US

[Inaba]

I've ordered some additional hardware that may help out with this, but it may not make a difference to this particular problem.  I think it may stem from the way EMC handles DGM when a new block starts, there's a bucket load of DB activity setting up the new miners for the new block, and there may be some queries that are holding everyone else up.  I will investigate that as well as how to best leverage the new hardware.

[cyberlync]

I've ordered some additional hardware that may help out with this, but it may not make a difference to this particular problem.  I think it may stem from the way EMC handles DGM when a new block starts, there's a bucket load of DB activity setting up the new miners for the new block, and there may be some queries that are holding everyone else up.  I will investigate that as well as how to best leverage the new hardware.

Crossing my fingers

[freshzive]

Wow, yeah, I just noticed that I get a ton of stales (rejects) at the beginning of a new block as well. West coast USA here. Kind of a bummer

[e21]

I've ordered some additional hardware that may help out with this, but it may not make a difference to this particular problem.  I think it may stem from the way EMC handles DGM when a new block starts, there's a bucket load of DB activity setting up the new miners for the new block, and there may be some queries that are holding everyone else up.  I will investigate that as well as how to best leverage the new hardware.

Crossing my fingers

Same here  It certainly would be nice to get that fixed

[Inaba]

I have the beginnings of a solution in my head for the new block problem, so it's something I will be working on in the immediate future.  It's going to require some changes to the way DGM is handled, so I need to do a lot of testing and checking before I put that type of fix into place.

[cyberlync]

I have the beginnings of a solution in my head for the new block problem, so it's something I will be working on in the immediate future.  It's going to require some changes to the way DGM is handled, so I need to do a lot of testing and checking before I put that type of fix into place.

If you need some help with testing, when it gets so far, let us know, I'm sure some of us would be happy to contribute.

[Inaba]

Yeah, I will definitely need some testing on it.  Maybe I can have something up this weekend, but I'm not guaranteeing it