Skip to content
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

Inter region comparisons #3

Open
St3ngah opened this issue Oct 10, 2020 · 4 comments
Open

Inter region comparisons #3

St3ngah opened this issue Oct 10, 2020 · 4 comments

Comments

@St3ngah
Copy link

St3ngah commented Oct 10, 2020

It would be great to add the feature to enable inter region comparisons.

@Burekasim
Copy link
Collaborator

How do you think we should present it? per machine type or a list with all the regions?

@St3ngah
Copy link
Author

St3ngah commented Oct 10, 2020

Not sure about the UX but maybe
1st option: a new button called "compare between regions", in that option we would select only 1 instance type or we would take the first one only, and on the next page the price list by region for that instance type. We would have a new column called "Region".
2nd option: maybe a bit more complex, same new button called "compare between regions", and on the next page the list of selected instances like the current one and some checkboxes to select the different regions we want to compare. Then for each instance, the price list by region, and the same new column "Region". Then you can sort the date through the table using all the different columns.
Just my 2 cents. Thanks for considering it anyway.

@nchicong
Copy link

+1

Ability to compare between regions would be nice.

We found an interesting fact that n2d-standard-4 spot/preemptible in Tokyo and US are half cheaper than most of regions in Asia & EU.

@AlexisBRENON
Copy link

Would it be possible to add the Region as a "standard" column.
For example, for machine type "e2-medium", you will have one row per region where it is available with the price for each region.
This would allow to filter on regions through the "Search" field of the column.
However, search field should be "improved" to allow some more complicated search request. Maybe supporting Regex can be an easy implementation while letting the burden to the user of crafting the right one for its use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants