Tag: spot

Home » Posts tagged "spot"

AWS 推出 EC2 Fleet：直接混搭標準 EC2、Spot、RI 的計算

AWS 將本來 EC2 的 Spot Fleet 加上了 EC2 Fleet，計算的公式從本來只有 Spot Instace，變成把標準 EC2 Instance 與 RI 的計算全部都納進來：「EC2 Fleet – Manage Thousands of On-Demand and Spot Instances with One Request」。

Today we are extending and generalizing the set-it-and-forget-it model that we pioneered in Spot Fleet with EC2 Fleet, a new building block that gives you the ability to create fleets that are composed of a combination of EC2 On-Demand, Reserved, and Spot Instances with a single API call.

不過目前有些服務還沒整，主要是跟 auto scaling 有關的部份，這部份應該是一次上一大包：

We plan to connect EC2 Fleet and EC2 Auto Scaling groups. This will let you create a single fleet that mixed instance types and Spot, Reserved and On-Demand, while also taking advantage of EC2 Auto Scaling features such as health checks and lifecycle hooks. This integration will also bring EC2 Fleet functionality to services such as Amazon ECS, Amazon EKS, and AWS Batch that build on and make use of EC2 Auto Scaling for fleet management.

整完以後對於要省成本就更簡單了...

AWS, Cloud, Computer, Murmuring, Network, ServiceNo Comment

EC2 的 Spot Instance 可以「接關」

Amazon EC2 的 Spot Instance 可以「接關」了：「New – Stop & Resume Workloads on EC2 Spot Instances」。

當 Spot Instance 的競價不足以標到機器時，他會先關起來 (Stop)，等到價錢低於競價後就會再打開機器，這時候的狀態就會恢復。另外也提到了必須是使用 EBS 的機器才支援：

Amazon EC2 Spot now allows Amazon EBS-backed instances to be stopped in the event of interruption, instead of being terminated when capacity is no longer available at your preferred price. Spot can then fulfill your request by restarting instances from a stopped state when capacity is available within your price and time requirements.

用法是把 Spot Instance 的關機設定設為 Stop：

To use this new feature, choose “stop” instead of “terminate” as the interruption behavior when submitting a persistent Spot request. When you choose “stop”, Spot will shut down your instance upon interruption.

恢復的時候就會儘量保持一樣地開回來 (連 instance id 都相同)：

When capacity is available again within your price and time requirements, Spot will restart your instance. Upon restart, the EBS root device is restored from its prior state, previously attached data volumes are reattached, and the instance retains its instance ID.

是個接關的感覺 XD

AWS, Cloud, Computer, Murmuring, NetworkNo Comment

EC2 與 EBS 十月開始以秒計費

雖然只是 Amazon EC2 與 Amazon EBS 計價模式的改變，但這次 AWS 的改變對於許多開發流程有很大的影響 (重點在 EC2 的部份)：「New – Per-Second Billing for EC2 Instances and EBS Volumes」。

10/2 開始改變 (而不是 10/1)，低消一分鐘，Windows 機種以及需要額外收費的 Linux 機種不在範圍內：

This change is effective in all AWS Regions and will be effective October 2, for all Linux instances that are newly launched or already running. Per-second billing is not currently applicable to instances running Microsoft Windows or Linux distributions that have a separate hourly charge. There is a 1 minute minimum charge per-instance.

然後 Spot 與買 RI 後也是一樣以秒計價：

List prices and Spot Market prices are still listed on a per-hour basis, but bills are calculated down to the second, as is Reserved Instance usage (you can launch, use, and terminate multiple instances within an hour and get the Reserved Instance Benefit for all of the instances).

這次改變的影響很巨大。馬上可以想到幾個情境...

第一個是對於實踐 Release early, release often 的團隊來說，如果設計成每 deploy 一次就建一個新的 AMI (最乾淨的作法)，再開新機器換掉的話，成本就會增加不少。所以對於這樣的團隊，就會偏好朝著替換現有目錄內的東西後重啟...

現在改成以秒計費後，直接透過 Blue-Green Deployment 就可以了 (AWS CodeDeploy 年初也支援了：「AWS CodeDeploy 支援 BlueGreenDeployment」)：(如果不熟悉 Blue-Green Deployment 的話，更白話的說法就是「先建後拆」...)

同樣的理由，對於 Auto Scaling 的 policy 也有些改變。之前機器開起來都會想讓他跑一個小時，所以 scale down 的部份都會寫的比較鬆一點。現在就可以重新規劃了...

另外一個影響是對使用 container 的誘因少了不少。很多人用 container 的用法是開大台機器再裡面拆給不同服務用，讓資源利用率變高，現在變成用多少算多少後就不太需要這樣了...

當然也還是有缺點。以前 Spot Instance 如果被 AWS 收回時，最後的那個小時是不計費的。現在因為以秒計費，變成要收費了...

最後是 10/2 生效這件事情頗怪，該不會是財務部門不願意配合 10/1 星期天加班生效，所以只好變成 10/2 生效這種理由吧... XDDD

AWS, Cloud, Computer, Murmuring, Network, ProgrammingNo Comment AWS, Cloud, Computer, Murmuring, NetworkNo Comment

Auto Scaling 可以拉 EC2 Spot Instance 進來用了

Update：auto scaling 在 2012 就支援 spot instance 了：「EC2 Spot Instance Updates – Auto Scaling and CloudFormation Integration, New Sample App」，我一直有 auto scaling 不支援的印象... 這次是支援 EC2 Spot Fleets (i.e. 以 capacity 為主的架構，將兩台 c4.4xlarge 與一台 c4.8xlarge 當作是有相同 capacity 來喊價)。

AWS 的 Auto Scaling 宣佈支援 Spot Instance 了：「New – Auto Scaling for EC2 Spot Fleets」。

雖然文章主要都是以 worker 之類的應用來做，但可以看到還是有說 web service：

Web Service – Scale web services based on measured response time and average requests per second.

我猜官方還是不建議這樣用，所以整篇文章都還是以 worker 類為主。應該是因為 web service 直接對使用者，用 Auto Scaling 不一定開的起來，反而有可能會爆炸 XD

AWS, Cloud, Computer, Murmuring, Network, WWWNo Comment

EC2 Spot Blocks：固定時間的 Spot Instances

EC2 設計 Spot Instances 提供某些應用程式可以用比較低廉的價錢租用機器，但缺點是隨時可能會中斷，所以程式必須定時記錄進度。

但不是每種應用程式都有辦法這樣做，所以一般遇到不能中斷的還是會用 On-Demand Instances 來處理。而現在 EC2 則提供了 Spot Blocks 來解決這個問題：「New – EC2 Spot Blocks for Defined-Duration Workloads」。

你可以設定 1 到 6 個小時的執行時間，時間到就會自動結束：

In order to make EC2 an even better fit for this type of defined-duration workload, you can now launch Spot instances that will run continuously for a finite duration (1 to 6 hours).

Spot Instances 與 Spot Blocks 是分開競價，大約比 On-Demand 便宜 30%～45%，同時在非尖峰時間另外會有 5% 的優惠：

Pricing is based on the requested duration and the available capacity, and is typically 30% to 45% less than On-Demand, with an additional 5% off during non-peak hours for the region. Spot blocks and Spot instances are priced separately; you can view the current Spot pricing to learn more.

AWS, Cloud, Computer, Hardware, Murmuring, NetworkNo Comment

EC2 Spot Instance 可以用 Capacity 競標了

前幾天 AWS 的「New – Resource-Oriented Bidding for EC2 Spot Instances」這篇文章提到 EC2 Spot Instance 可以用 capaciy 競標了，也就是以「資源的總量」來飆，而非指定某種型態的 instance。

以文章裡的例子來說，假設要標 488 個單位的 capacity，那麼有可能出現：

  • 2 x r3.8xlarge
  • 4 x r3.4xlarge
  • 8 x r3.2xlarge
  • 16 x r3.xlarge
  • 32 x r3.large

也有可能出現混搭的版本：

  • 1 x r3.8xlarge and 2 x r3.4xlarge
  • 2 x r3.4xlarge and 8 x r3.xlarge
  • 8 x r3.xlarge and 16 x r3.large

對於某種 spot instance 價錢突然提高時，可以改用其他 instance 繼續執行，變得更有彈性...

AWS, Cloud, Computer, Murmuring, NetworkNo Comment AWS, Cloud, Computer, Murmuring, NetworkNo Comment

Google Cloud Platform 也推出了類似 Spot Instance 的產品

Google Cloud Platform 推出了類似於 Amazon EC2 的 Spot Instance 的產品，叫做 Preemptible VM：「Introducing Preemptible VMs, a new class of compute available at 70% off standard pricing」。

不同的是，沒有引入競價系統，而是固定的 discount。另外有一些限制，像是最多持續 24 小時：

The tradeoff is that Preemptible VMs are limited to a 24 hour runtime, and will sometimes be preempted (shut down) earlier than that.

而停機通知時間比 Spot Instance 短，只有 30 秒 (相較於 Spot Instance 有兩分鐘)：

When Preemptible VMs are terminated, they'll receive a 30 second notice allowing you to shutdown cleanly (including saving work, if applicable).

Cloud, Computer, Murmuring, NetworkNo Comment

Amazon EC2 Spot Instance 的關機通知

AWS 改善了 EC2 Spot Instance 的關機通知，在決定 terminate 前兩分鐘 instance 可以得知消息，讓 instance 可以處理「後事」，像是將計算的資料寫回 EBS 或是 S3：「New – EC2 Spot Instance Termination Notices」。

Today we are improving the reclamation process with the addition of a two-minute warning, formally known as a Spot Instance Termination Notice.

不過目前不是 trigger，而是透過 polling 的方式提供：

The Termination Notice is accessible to code running on the instance via the instance’s metadata at http://169.254.169.254/latest/meta-data/spot/termination-time. This field will become available when the instance has been marked for termination (step 3, above), and will contain the time when a shutdown signal will be sent to the instance’s operating system.

建議的 polling 時間是五秒鐘一次：

We recommend that interested applications poll for the termination notice at five-second intervals.

至少有方法得知了...

AWS, Cloud, Computer, Murmuring, NetworkNo Comment

Recent Comments

Archives

Blogroll