google_cloud_platform
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
google_cloud_platform [2018/12/19 11:31] admin |
google_cloud_platform [2019/01/04 16:29] (current) admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Google Cloud Engine ===== | + | ## Google Cloud Engine |
| - | ===GCE是什麼？=== | + | ### GCE是什麼？ |
| 那么GCE很像传统上大家所熟悉的伺服器，但它假設在Google自己的數據中心，由專人維護，並且通過Google超快速的全球私有光線網絡互相連接。 | 那么GCE很像传统上大家所熟悉的伺服器，但它假設在Google自己的數據中心，由專人維護，並且通過Google超快速的全球私有光線網絡互相連接。 | ||
| Line 17: | Line 17: | ||
| - | ===== BigQuery ===== | + | ## BigQuery |
| - | === Design === | + | ### Design |
| BigQuery provides external access to the [[Dremel (software)|Dremel]] technology, a scalable, interactive ''ad hoc'' query system for analysis of read-only nested data. To use the data in BigQuery, it first must be uploaded to [[Google Storage]] and in a second step imported using the BigQuery HTTP API. BigQuery requires all requests to be authenticated, supporting a number of Google-proprietary mechanisms as well as [[OAuth]]. | BigQuery provides external access to the [[Dremel (software)|Dremel]] technology, a scalable, interactive ''ad hoc'' query system for analysis of read-only nested data. To use the data in BigQuery, it first must be uploaded to [[Google Storage]] and in a second step imported using the BigQuery HTTP API. BigQuery requires all requests to be authenticated, supporting a number of Google-proprietary mechanisms as well as [[OAuth]]. | ||
| - | === Features === | + | ### Features |
| * **Managing data** - create and delete tables based on a JSON-encoded schema, import data encoded as CSV or JSON from Google Storage. | * **Managing data** - create and delete tables based on a JSON-encoded schema, import data encoded as CSV or JSON from Google Storage. | ||
| * **Query** - the queries are expressed in a standard SQL dialect[6] and the results are returned in JSON with a maximum reply length of approximately 128 MB, or an unlimited size when large query results are enabled.[7] | * **Query** - the queries are expressed in a standard SQL dialect[6] and the results are returned in JSON with a maximum reply length of approximately 128 MB, or an unlimited size when large query results are enabled.[7] | ||
| Line 28: | Line 28: | ||
| * **Access control** - is possible to share datasets with arbitrary individuals, groups, or the world. | * **Access control** - is possible to share datasets with arbitrary individuals, groups, or the world. | ||
| + | |||
| + | ## Cloud ML | ||
| + | |||
| + | 1. Cloud Machine Learning Engine：用户自己提供算法。在本地機器上進行的機器學習訓練时data的整理和机器的scaling是很麻烦的，GCP可以自动帮忙做这些。 | ||
| + | 2. Cloud AutoML、Natural Language和Vision等：用户提供Data。 | ||
| + | 3. Cloud Speech-to-Text API、Cloud Video Intelligence等：Google训练完成的。用户不需要提供Data。 | ||
| + | |||
| + | ### Note | ||
| + | |||
| + | - Unordered List Item Google Cloud ML使用的 ML frameworks: TensorFlow, scikit-learn, XGBoost, Keras. | ||
| + | - 谷歌自己研发的ML专用芯片 —— TPU：the TPU is on average about 15X-30X faster than its contemporary GPU or CPU, with TOPS/Watt about 30X - 80X higher. Moreover, using the GPU’s GDDR5 memory in the TPU would triple achieved TOPS and raise TOPS/Watt to nearly 70X the GPU and 200X the CPU. [[https://arxiv.org/pdf/1704.04760.pdf]] | ||
google_cloud_platform.1545190317.txt.gz · Last modified: 2018/12/19 11:31 by admin