![]() ![]() So when the demand for on-demand instances increases there are less spares available, and the availability of spot-instances decreases driving spot pricing higher according to competing spot-bids. This stems from Amazon EC2 statement that you " bid on spare Amazon EC2 instances". This is not a bug, this is an priority / availability issue because on-demand instances have priority over spot-instances regardless of spot-bids. Why would you pay above on demand for a single server?). ![]() (I would discount this since they would presumably launch them at a price which would be below the minimum on demand price. Some company launched 1000 servers at once, and wants to make sure that they all launch. (I would discount this since it would be ridiculous and bad business) Someone entered $1.2 instead of $0.12 (I would discount this since it happened 20 times over the space of 3 weeks).Īmazon regularly artifically inflate their prices by bidding on their own instances to get the most bang for their buck. If you look at zone-b again for small instances, there is a similar, spike frequently. This is some 6 times the actual on demand price. But for a period of a few weeks, in zone B, the price would regularly spike to $1.20. If you look at a lot of the instance prices for spot instances, you will notice regular patterns of spikes.Īs you can see, the price for this compute medium instance, regularly spikes above the on demand price.Ī c1.medium instance (on demand), would only cost $0.186 per hour. This is something which will be best explained through screenshots of a historical chart of instance pricings. Amazon Pricing on Spot Instance Inconsistencies
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |