Quote
How do you manage dropping hashrates? I plan to run my Spot Instances for up to a week at a time and after about 12 hours, my hashrate dropped from an average of 135-160 to 99. I checked my instances and one of them has dropped from 100% CPU to 0%, is this normal? This has happened to two of my fleets, where one instance just drops in CPU usage.
This seems to be a resource issue with AWS, there is no real way around it unless you monitor all instances using multiple ssh connections, for example with Windows you can use MTPuTTY or with Linux you can use Pac
Quote
I have managed to receive a limit increase from 5 to 25 for m5.large, when do you suggest I request more and how much is a good amount to request without going overboard?
I would give it a week before you apply for more and see how it goes
Quote
Is there a larger server, similar to m5.large that produces efficient hash rates for the cost? I'd love to increase my hash rate for a similar cost (i.e instead of $0.0163 per hour for m5.large, is there a server that costs double the price that offers double the hashrate?)
Value for money wise, the m5.large is really the best at the moment, and seeing as Ohio is currently the cheapest region, you should really try and increase your limits there for the moment. Prices do fluctuate and it is an idea to keep any eye on them, as sometimes the time of day can make a difference.
I appreciate the response brother. If I terminate a Spot Instance through the Instances page (where it lists my 25 individual instances), will it redeploy, since I set it on Request & Maintain? If so, is that an alternative solution for the instances that drop in CPU usage?
It should do, yes. But sometimes you only need to do a sudo reboot on the ssh client to get it back up to speed again
