All Tags
AWS
algorithm-design
architecture
cloud-principles
cost-reduction
data-centric
data-compression
data-processing
deployment
design
edge-computing
energy-footprint
hardware
libraries
locality
machine-learning
management
measured
migration
model-optimization
model-training
performance
queries
rebuilding
scaling
services
strategies
template
workloads
Tactic: Use spot instances
Tactic sort:
Awesome Tactic
Type: Architectural Tactic
Category: resource-allocation
Tags:
AWS
Title
Use spot instances
Description
AWS EC2 spot instances allow access to spare EC2 capacity. These instances are offered for a discounted price. The catch is that these instances are only offered if there are available resources and can be retracted at a two-minute notice. Hence, they are suitable for fault-tolerant, stateless applications. The energy consumed by software will not reduce when using spot instances. On the contrary, as the software needs to perform extra tasks to be compatible with spot instances (e.g., storing intermediate states), the overall energy consumption of the program might even increase. Nevertheless, spot instances allow the use of spare capacity, instead of requesting AWS to run more physical machines for the on-demand workload. Hence, more output is produced for relatively little extra energy. Thus, using spot instances might have a positive effect on energy efficiency. This effect is, however, difficult to assess as there is little transparency on the internal processes of the spot instances architecture.
Participant
Cloud consumer
Related software artifact
AWS spot instances
Context
Public cloud
Software feature
< unknown >
Tactic intent
Taking advantage of discounted resources for fault-tolerant and stateless applications
Target quality attribute
Cost-efficiency
Other related quality attributes
< unknown >
Measured impact
< unknown >
Source
Master Thesis “Architectural Tactics to Optimize Software for Energy Efficiency in the Public Cloud” by Sophie VosGraphical representation
