Quote from: sundownz on February 03, 2018, 03:53:18 PM

Quote from: jagauthier on February 03, 2018, 03:50:15 PM

Quote from: sundownz on February 03, 2018, 03:44:38 PM

Quote from: crackfoo on January 26, 2018, 02:56:41 PM

Quote from: jagauthier on January 26, 2018, 12:23:05 PM

zpool's API has some kind of limitation on it. If you poll it too quickly it returns nothing. Thus, appearing down.

If my miner has just polled the API, and then I restart it, 9 times out of 10 the API return is blank. Yes, it's very annoying.

1 query every 10s is the limit.

I assume this is done by IP address?

I have a huge number of workers at one location so I end up having machines get stuck on the same algo for many hours as they cannot get an API update.

Any ideas on a possible solution ? Is there a way to have the API check by IP & also the Worker ID -- I do assign each worker a unique ID.

The API has no idea about your worker ID. It's just an HTTP call.

I see. ZPOOL is my favorite but with so many workers on one IP algorithm switching simply doesn't work correctly.

I've been on Ahashpool for a week or so now and I simply don't like it as much for various reasons (slow stats, less info on the stats page, fewer coins, etc)... but the API doesn't time out and things swap as they are supposed to.

Yeah, the API limitation is archaic. Any decent service should be able to handle calls to its API without a problem.