Noticing LOTS Of "warning job finished: miner is idle" using poclbm on testnet

[gigabytecoin]

Like every time I mine a block almost, I am told that the miner is idle.

Could it be that since I am personally mining about 16 blocks per hour that the small bitcoin testnet distribution is not verifying these transactions fast enough?

I have just begun to run phoenix miner in an attempt to see if it is just the miner... however I have run both miners on the regular blockchain recently and have not received this number of "job finished" errors...

There appear to be smooth runs of poclbm miner that show next to no "miner is idle" warnings for quite a few blocks in a row, and then all miners seem to go to spotty chunks of mining time where every other block found there is a "miner is idle" warning.

Could it also be that I am maxing out my "m1.large" EC2 instance in terms of power? (I highly doubt it however, as it is showing between 99% and 100% "idle" CPU with all other values at or near 0% in the linux top command.

I am showing 27 connections on testnet. My port is forwarded.

There are approximately 10 5870s on 2 machines transmitting about 3,7Ghps from my home to the amazon cloud.

I will report back with the results from phoenix miner.

[gigabytecoin]

Ok back with an update.

I tried running both poclbm and phoenix miners on multiple different video cards against bitcoind on port 8332 running testnet.

Both miners showed considerable "miner is idle" messages in between solved blocks for a number of hours.

I also have pushpool running on the same server.

I just switched one of the miners over the port 8344 and am mining shares through pushpool now (all other settings are the same) and thankfully pushpool is doing it's job flawlessly. A few hundred shares found so far with no "miner is idle" messages.

So I guess bitcoind just doesn't function exactly as expected when you are controlling 75%+ of the network... who'd a thunk?!