googlecloudplatform / region-picker

Tool to help you pick a Google Cloud region considering carbon footprint, price and latency.

Google Cloud Region Picker

Helper tool to pick a Google Cloud region, taking latency, price and carbon footprint into account.

To contribute to this project, see CONTRIBUTING.md.
To update the data, see UPDATING.md.

The main branch of this repository is automatically deployed to cloud.withgoogle.com/region-picker via cloudbuild.yaml.

Code by @steren, Design by @mau_rs

region-picker's Issues

Icons for dark mode

In dark mode, icons appear black on black

Make it clear which regions are covered by the tool.

Add view transitions

Add Warsaw (europe-central2)

GCP region Warsaw (europe-central2) is available but not in the tool yet.

This is because carbon data for europe-central2 is not yet available here.

It will hopefully be added to 2020 refresh of the carbon data.

Not loading properly is trailing / missing

getting the following error in the chrome console. The tool doesnt propoerly load up

Access to link element resource at 'https://cloud.google.com/' (redirected from 'https://cloud.withgoogle.com/data/countries.json') from origin 'https://cloud.withgoogle.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Measure real latency to GCP region instead of using current location

Instead of prompting for current location, we could do like https://gcping.com and send requests to Cloud Run services deployed on every GCP regions and measure latency.

The optimizer would then need to en adjusted to take latency into account in addition to geo coordinates.

Hosting Cloud Run services in many GCP regions comes with an additional maintenance burden and costs, and adds server side dependencies to this tool.

It is unclear if this is worth the investment.

support regions with no carbon data

Carbon data is updated once a year for regions launched the year before.

it is published on this site and on GitHub

However, Google Cloud launches new regions regularly. It would be useful to be able to add them to this tool before carbon data is available.

This tool would need to be updated so that:

• its algorithm properly handles carbon data not available
• if the "carbon" slider is > 0, we should display a warning that carbon data is missing for some regions and therefore they won't be considered unless the carbon slider is set to 0.

Use more GCP products for price.

E2 instances might not be representative.

Probably should be coupled with #17

Display more info in results

In the result list, display more of the region info

Product regional availability

similar research @ https://github.com/PatMyron/cloud and feature availability is a most important factor in region selection

Store parameters in URL

The parameters of the optimizer could be stored as URL parameters, either by default, or when users click "Share".

This would allow users to share their results by sharing a URL

Use a official pricing CSV export instead of manual JSON

add me-central2 region

lowest latency region for saudi arabia should be me-central2 (Dammam) but it is currently showing a different region. is it possible to add all new locations in middle east to the list?

Please add me-west1 region

Thanks

Some high carbon regions have 3 leaves

Leaf rendering seems to have an issue: Jakarta shouldn't have 3 leaves.

It doesn't seem to affect the region sorting. The problem likely comes from the code that translates carbon info into number of leaves

Hong Kong region (asia-east2) not showing as top pick for traffic coming from Hong Kong

Hi, I was trying to put latency as the only decision factor and specifying traffic coming from Hong Kong, it is strange that the Hong Kong region (asia-east2) doesn't show up as the top choice. In fact, it doesn't even appear among the top 6 choices.

Carbon footprint rating

If I filter the regions with 100% Lower carbon footprint, 0% Lower price and 0%Lower latency. It ranks regions only using Carbon Free Energy percentages. Surely this is incorrect because when a region is not using carbon free energy it should take into account the Grid carbon intensity too. For example:
us-central1 has a Carbon Free Energy: 93% and a Grid carbon intensity: 454 gCO2eq/kWh. This means 7% of the time it uses 454 gCO2eq/kWh, and on average it is 0.07* 454 = 31.78gCO2eq/kWh.

us-west1 has a Carbon Free Energy: 90% and a Grid carbon intensity: 78 gCO2eq/kWh. This means 10% of the time it uses 78 gCO2eq/kWh, and on average it is 0.10* 78 = 7.8gCO2eq/kWh.

Yet us-central1 is showing up better on the Lower carbon footprint ranking than the us-west1.

Product list sometimes shows duplicates

Probably a race condition at initialization

Save Countries Selected and add to output

The where is your traffic coming from drop down is too small.
There may be better UI widgets for a multiselect list.
Once a country is selected, it should be added to the output.
The site should produce a report that engineers can submit to the greater powers to backup their recommendation or decision.

Maybe add another parameter for features only supported in some regions, like vertex-ai managed notebooks for one example, or certain CPU or GPU types. Without getting too complex.

If the user clicks "I need Vertex-AI managed notebooks" then those regions could be filtered out of the result.