Topic: Anybody generating on Amazon EC2? (Read 17726 times)

This thread is from 2010 you retard.

I have not personally mined from AWS, but faced one situation in our project where one of the project member committed the public key into github and next day we get a call from  AWS saying our account has been billed like 1500x times the normal billing. There was no AWS administrator in our firm till that time and this leaked key was used by the hacker to create hundreds of spot instances. This has been used to do the btc mining, we terminated all the instances as soon as we got it. Not sure how many they managed to get, but the way so many instances were created, i feel if we are like getting a good mining to happen, we may need to invest heavily.

Be careful trying to value a VM in bitcoins..

You will generate less and less with the same hardware over time, by design.  As the number of blocks grows the difficulty increases proportionally to the rate at which the generation is happening so it will always slow down.  If you have a big chunk of the network's compute power you will be generating more than other people but even if you're generating 10 an hour today, in a few weeks you'll be down to a couple a day and everyone else with lesser capabilities will be down to a couple a month.

This is all just an artificial way to limit supply to direct the focus to trading rather than just generating, as I understand it.  If everyone is mining gold in their back yard and hoarding it in their garage, it's kind of worthless.  But once the supply of gold starts running out and most of it has been mined (or if you need to dig for 10 years to find an ounce of it), if you want gold you need to trade something for it.. so by design the supply will diminish.

I have access to a couple of VPS instances running on Xen that often have a LOT of spare cycles. Since the only thing I'm billed by usage on is bandwidth, I might as well get my money out of the things.

The cheapest one I have is $8 / month. They don't give any good info about CPU strength (and are generally unreliable), but at that price you only have to generate about 1.3 blocks a day, or one every 18.5 hours. That's still a bit high, but even if I only make $4 a month, that's a nice dividend since making BitCoins isn't what this box is primarily all about.

One Amazon "EC2 compute unit" is, according to them, approximately equal to a 1ghz 2007 Xeon processor (that's a m1.small).

Judging by my laptop generating experience, there's no way an m1.small instance would generate enough ฿ to be profitable.

The heftiest instance you can buy ("large CPU") is 20 units big, and costs $0.231 per hour; with bitcoins selling for about a half a penny each it would have to generate 46 per hour (or about a block an hour) to break even.  Ummm.... no, that does not compute.

RE: how did I get hashes-per-second on my mac:  I applied laszlo's patch to a version I compiled from source code.

I haven't tried that. Just got an AWS account, though. Their storage solution looks interesting ($0.10 / GB).

Have you read about Spot Instances? You can set a maximum hourly price that you're willing to pay in order to keep your server up. The "ask" price from Amazon fluctuates with supply and demand. If the BitCoin app could be made to save frequently and recover from downtime quickly, you could set your spot price to something that you know will make you profitable.

Just set your maximum bid price to:
(max bid price) = (blocks / hour) * (coins / block) * (USD / coin)
Where blocks per hour is how many blocks you expect / test to generate in an hour. That's the only tricky part of the equation.

Until recently, the "ask" price for a m1.small instance appears to have been hovering around 2.9 to 3.1 cents USD. There was a somewhat prolonged spike to 6 or 7 cents lately, but that might not continue. At an average spot price of $0.03 / hour and an exchange rate of $0.0041 / Bitcoin, you would need to generate one block every 6.8 hours, or 3.5 blocks per day. Is that unreasonable? Probably, but I'm not sure how fast a m1.small instance is. Also, that assumes that your instance is generating blocks for every moment it is up, which isn't true, since the instance has to reload and restart every time it goes down. On the flip side, Amazon doesn't charge you for partial time if you get shutdown (or perhaps they don't charge you for the ENTIRE hour -- it's a bit unclear).

It's an interesting idea, and might work well for you.

By the way, how did you get a metric on how many hashes your Mac checks per hour?

Has anybody tried generating bitcoins on Amazon EC2 instances?  If you have, how many coins/day are you getting (and on what type of instance) ?

If nobody has already, I might do some experimenting and get some back-of-the-envelope estimates for $/bitcoin using Amazon EC2 spot instances.

(I've had zero luck generating any coins over the last week on my couple-year-old Macbook Pro, which only does 150-200K hashes per second)