All Tags
AWS
ai
algorithm-design
architecture
browser
cloud
cloud-efficiency
cloud-principles
cost-reduction
data-centric
data-compression
data-processing
deployment
design
documentation
edge-computing
email-sharing
energy-efficiency
energy-footprint
enterprise-optimization
green-ai
hardware
libraries
llm
locality
machine-learning
maintainability
management
measured
microservices
migration
mobile
model-optimization
model-training
multi-objective
network-traffic
parameter-tuning
performance
queries
rebuilding
scaling
services
storage-optimization
strategies
tabs
template
testing
workloads
Tactic: Use asynchronous I/O
Tactic sort:
Awesome Tactic
Type: Software Practice
Category: green-software-practice
Tags:
energy-footprint
Title
Use asynchronous I/O
Description
Using asynchronous I/O with Native Command Queuing is more energy efficient than synchronous I/O because decrease the time it takes to process a job.
Participant
Software application developers
Related software artifact
RPC between 2 servers, use file transfer (e.g. SSH/FTP)
Context
Green Lab
Software feature
< unknown >
Tactic intent
Use asynchronous I/O
Target quality attribute
Energy-efficiency
Other related quality attributes
< unknown >
Measured impact
< unknown >
Source
Procaccianti, G., Fernández, H., & Lago, P. (2019). Green Software in Practice: Empirical Validation and Assessment of Best Practices for Writing Energy-Efficient Software. Vrije Universiteit Amsterdam, October 2019.Graphical representation
