Bitcoin-mining-proxy help

[smracer]

Hello,

I am hoping someone can help me out.

I have been running bitcoin-mining-proxy for about a week and for some reason people are getting "Pool not delivering work fast enough" messages sometimes.

The server is a dual quad core Dell with 16GB ram at a large colo facility.  The load averages are at .05 when I have 200GH+ running through it.  CPU 98% idle.

When I first got it running I was getting PHP PDO errors once I got over 100GH.  So I upped the PHP max connections to 5000 and I have seen no more errors whatsoever.

Nothing in apache2 error.log anymore.

But still some people are getting "pool not delivering work fast enough" messages.  Are there any other settings I need to change?  Anything in apache2.conf?

Thank You.

Bo

[kakobrekla]

That client side issue can prolly be fixed by increasing the getwork timeout in the miner sw.

Also, if you take a look at place_json_call() in common.inc.php, you can see it uses inefficient file_get_contents call. Use curl instead.
(benchmark: http://stackoverflow.com/questions/555523/file-get-contents-vs-curl-what-has-better-performance )

That might give you some space.

If its a source pool problem, in that case, you can tune timeout for your outgoing connections in the place_json_call() as well.
I know I bumped mine up from the default.