如何正确阻止Google Cloud Datalab [英] How to correctly stop Google Cloud Datalab

查看:118
本文介绍了如何正确阻止Google Cloud Datalab的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

使用数据在Junyper / Datalab中是一种乐趣,但我不希望它变得昂贵。


$ b

登录和部署。这将需要6或7分钟。一旦部署,启动并运行,您可以直接进入树状结构并恢复工作。你可能会说10分钟的上衣。


Playing with data is a joy in Junyper/Datalab, but I do not want it to become costly.

Google recommends:

"You can minimize compute charges by stopping/restarting Cloud Datalab instances."

However, if I stop the AppEngine instance or the Compute Engine VM instance, they simply restart ...

So how to correctly stop/pause Google Cloud Datalab, so that I'm only charged for my use, not for the idle time? Is there some kind of trigger that restarts the instances?

解决方案

Here's what I'm doing. I like keeping everything in the cloud; but, I want to resume work with minimal fuss and cost.

Save Data/Source and Delete Datalab

1. Commit changes to Your Cloud Git Repository. As long as the source changes are committed, they'll pop backup when you re-create google cloud. Keep your data in buckets gs://... or BigQuery. Commit all changed Notebooks.

Your Cloud Git Repository

2. Delete the datalab module.

https://console.cloud.google.com/projectselector/appengine/versions?moduleId=datalab

Resuming Your Work:

When you're ready to resume your work, goto launch cloud datalab sign-in, and deploy. It will take 6 or 7 minutes. Once it's deployed, up, and running, you can go directly to your tree and resume your work. You're probably talking 10 minutes tops.

这篇关于如何正确阻止Google Cloud Datalab的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆