Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/6925c674-3858-8009-852a-bd8fdd5679ae
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== 1. TPU 是「Google 內部 + 綁死在 GCP 的方案」 ==== TPU 本質比較像: : 一台只在 Google 自家機房出沒的專用機器, : 你只能透過「上 GCP / 用 Vertex AI」來間接使用。 也就是說: * 你不能像買 H100 一樣買一堆 TPU 回去自建機房。 * 多數公司要上 TPU 就等於: - 把 infra 綁死在 GCP - 或至少要建立一整套「專門跑在 GCP TPU 上」的 pipeline。 對很多大客戶來說,問題就來了: * 我原本用 AWS/Azure,難道為了 TPU 要整套搬家? * 我公司政策要 multi-cloud,TPU 是 Google 專有,那其它雲端怎麼辦? * 我未來想自己買機櫃做 on-premise,TPU 根本買不到。 → 所以 TPU 的「市場」天生就被限制在:願意 heavily 綁定 Google 生態的那一群人。
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)