-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS impacts #29
Comments
Implementation is done. Need to integrate data from : |
CSV file for AWS archetype can be found here : We still need to complete the missing die size for the CPU family used in AWS archetypes. |
Problem
Implement the impact of Amazon Web Services (aws) cloud instances
Solution
Using archetype. Each cloud instance type will be saved as an archetype. The user send the name of the instance under study to choose which archetype to load and usage data to precise the archetype.
Manufacture and usage are measured with the classic server methodology and divided by the number of instance type per server (depending on the instance type).
By default (in the archetype), the instance is load at 50% 100% of the time. This can be override by the user.
Additional context or elements
AWS archetype exemple (fake datas)
Example of request
querry parameter :
a1-4xlarge
The text was updated successfully, but these errors were encountered: