Your liability is not capped anywhere. I better stick to 5$/mo DO for my side-projects.
Deploy your side-projects at scale for basically nothing – Google Cloud Run
81–90 of 397 posts
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#82Is there an easy equivalent for scheduled tasks in GCP? A background process that executes for a short period of time and then exists only charging you for the time it ran?
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#83Earlier quoted context omitted.
It‘s slready like a meme: the typical comment on the google cloud that it could be closed tomorrow. When will everyone understand that google cloud (money earning product) is different to all the other free products
> When will everyone understand that google cloud (money earning product) is different to all the other free products When Google demonstrates it. They've already discontinued various parts of their cloud product. True, they are unlikely to shut down gmail, search, or Android. On the other hand google's cloud is a money loser that has slipped to a distant #4 in the cloud rankings. But like many of Google's revenue-ge…
Do you have examples of discontinued Google Cloud Platform products?
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#84I've been using Cloud Run for my GPT-2 text generation apps ( https://github.com/minimaxir/gpt-2-cloud-run ) in order to survive random burst, and also for small Twitter bots ( https://github.com/minimaxir/twitter-cloud-run/tree/master/h... ) which can be invoked via Cloud Scheduler to utilize the efficiency benefits. It has been successful in those tasks. The only complaint I have with Cloud Run now (after many usab…
I'm currently serving an api that uses a 500mb resnet v2 model. The bootup takes to long, so now I have a single instance that can't handle any peaks and costs too much. Doesn't your model take to long to spin up before being able to serve a request ?
From: https://github.com/ahmetb/cloud-run-faq#how-to-keep-a-cloud-...
---
How to keep a Cloud Run service “warm”?
You can work around "cold starts" by periodically making requests to your Cloud Run service which can help prevent the container instances from scaling to zero.
Use Google Cloud Scheduler to make requests every few minutes.
Does my application get multiple requests concurrently?
Contrary to most serverless products, Cloud Run is able to send multiple requests to be handled simultaneously to your container instances.
Each container instance on Cloud Run is (currently) allowed to handle up to 80 concurrent requests. This is also the default value.
What if my application can’t handle concurrent requests?
If your application cannot handle this number, you can configure this number while deploying your service in gcloud or Cloud Console.
Most of the popular programming languages can process multiple requests at the same time thanks to multi-threading. But some languages may need additional components to do concurrent requests (e.g. PHP with Apache, or Python with gunicorn).
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#85Another option is Google Cloud AppEngine. It’s a little more limited in terms of languages that are supported, but the free tier is generous enough that I have never paid anything to run backends for side projects.
GAE and Cloud functions are gradually going to be replaced by Cloud Run. In fact Run and 2nd generation GAE run on exactly the same infra backed by gVisor and you can deploy custom containers to either in almost exactly the same manner.
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#86The thing I really want out of these services is the ability to set a payment cap. It’s probably never going to be an issue, but I have anxiety, and I can’t sleep easily knowing that if I fuck up, if someone sinister abuses my application or whatever I may be stuck with a giant bill.
Do-able today with GCP Billing
I wonder how friendly the UI is to accomplish that
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#87There must be added cost for a managed databases or similar, right? This sounds a lot like aws lambda (except nicer thanks to just running any container). In AWS’s case, you need to pay extra for RDS, redis, and any other persistence.
Exactly. And this is why I do not use these services yet. It's great if the app itself only costs like 18 cent per month.. But if you have to pay almost €10 per month for a (SQL) database, all the monetary benefits are gone.
I currently pay 7€ for two VPS which perform great, have a lot of storage and enough power to run all my projects.
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#88The thing I really want out of these services is the ability to set a payment cap. It’s probably never going to be an issue, but I have anxiety, and I can’t sleep easily knowing that if I fuck up, if someone sinister abuses my application or whatever I may be stuck with a giant bill.
That's not a bug... that's a 'feature'. Interestingly, AWS will not cut you off for non-payment (we had an issue with finance and were 250k in the red by the time we got the first 'Is there any issues over there?' email)
If you have a payment agreement, GCP won't cut you off provide your account is in good behavior in the past.
If your only payment method is credit card, IMHO allowing a past due account to continue generating cost is a very risky move and an easy target of abusing (imaging stolen credit card etc).
Disclaimer: I work for Google Cloud as SRE and have first hand experience dealing with past due account (it was highly manual and not automated).
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#89Earlier quoted context omitted.
Disclaimer: I work closely on Cloud Run as an SRE. IF you want, you can still have it by use "Cloud Run for Anthos", and deploy your container to your GKE cluster with the same Knative API. This allows you to have more control on memory/CPU etc.
Thanks, although unfortunately I'm not in the price bracket for Anthos (starts at 120k/year or so I believe).
I believe there's no requirement if you just want to use Anthos on GKE (I could be wrong though, Anthos is relatively new).
Alternatively, if what you really want is the ease to manage and deploy containers and automatically scale according to traffic, my understanding is you can always use the open source Knative project with your Kubenetes cluster. This provide you the exact same API supported by Cloud Run and makes it very easy to migrate from managed Cloud Run to on-prem K8s cluster (or K8s clusters from other Cloud vendors).
Re: Deploy your side-projects at scale for basically nothing – Google Cloud Run
#90He mentions CloudSQL for storage. Anyone know if it’s also on-demand?