News for hackers. Stuff that matters.

helpfulgoogler

Re:What is Google doing with its open source teams? on Sunday January 29, 2023 @11:31AM (#34569650)
I think you may be misreading the situation. When Anthos was announced, it didn't exist yet. They didn't have anything to sell you and you weren't important enough to be trusted with that knowledge. In this regard, your comparison was probably apt (especially if you were inquiring about Watson).
Re:Background Features in Google Meet, Powered by Web ML on Monday November 02, 2020 @01:49AM (#24965339)
Not what you asked for, but you can mute/unmute quickly with the keyboard shortcut: ⌘/Ctrl + d
Cloud Run is compatible with the Knative open source project, so you should be able to take your apps to a different cloud like you would with Kubernetes.
Re:Low-Cost VPS Testing on Tuesday December 10, 2019 @03:53PM (#21756737)
Yes. There is a proxy in front of the database which only allows whitelisted traffic (dangerous) or traffic with a valid cert (safe).
Re:Low-Cost VPS Testing on Tuesday December 10, 2019 @03:51PM (#21756726)
Although a public IP address is required, you don't need to poke any holes in the firewall. As a result, it is not a problem from a security perspective.

https://cloud.google.com/sql/docs/mysql/connect-run

Re:Low-Cost VPS Testing on Tuesday December 10, 2019 @03:48PM (#21756697)
Have you seen the instructions for using a Unix socket with Cloud SQL from Cloud Run?

https://cloud.google.com/sql/docs/mysql/connect-run

Re:App Engine’s New Go 1.11 Runtime on Tuesday October 16, 2018 @10:40PM (#18235687)
cgo is supported.
According to [1], the standard quota is 1,000,000 invocations per 100 seconds and can be increased. Maybe try asking again for increased quota? If the documentation is incorrect, please file an issue [2].

Counter-intuitively, ending the response before processing the data may actually be hurting your p99 response time. According to [3], instances which are not currently handling a request get very little CPU and generally don't make any progress. This means that this work will still be waiting to be done when the next request comes in and can slow it down. You may even end up with an instance trying to process several requests' data and also trying to handle another request on top of that. This last request is going to get an overloaded instance and likely be very slow. Further, the function isn't guaranteed to ever be run again, so that deferred work might not even ever happen.

It probably will cause you to use more of your invocations per 100 seconds quota, but you really shouldn't start background processing tasks in a Google Cloud Function that continue after completing a request.

[1] https://cloud.google.com/functions/quotas [2] https://issuetracker.google.com/issues/new?component=187195&... [3] https://cloud.google.com/functions/docs/bestpractices/tips