denoland / denoland/deploy_feedback

Migrate/Use Google Cloud Axion CPU to save cost and increase performance

Open
#752 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

### What problem are you trying to solve?

Deno deploy should run on top of this [Axion CPU](https://cloud.google.com/blog/products/compute/try-c4a-the-first-google-axion-processor) vm.

### Describe the solution you'd like

If we can save cost in running deno deploy then it would be fine for deno company and deno community also. so if deno deploy will be running on such [Axion CPU](https://cloud.google.com/blog/products/compute/try-c4a-the-first-google-axion-processor) then it will be huge cost savings.

### Describe alternatives you've considered

There is no alternatives.

### Documentation, Adoption, Migration Strategy

https://cloud.google.com/blog/products/compute/try-c4a-the-first-google-axion-processor

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.