Hey man, love your videos. Are you able to do anymore videos around Tensorflow or Deep Learning with Go? Some of the best Go vids on YT. Wish you could post more as they are so good.
Great and quick tutorial. But one question. I have the identical code used to test cloud functions. But for me the logs says: "Function execution took 152 ms, finished with status code: 200" - 152 ms?!? This slow?
Starting a new function instance involves loading the runtime and your code. Requests that include function instance startup (cold starts) can be slower than requests hitting existing function instances. If your function receives steady load, however, then the number of cold starts is typically negligible unless your function frequently crashes and requires restarting of the function environment.
@@packagemain I already ignored the cold start execution time of ~2.000 ms. This example of 152 ms was after 10 executions. And every function-call was between 150-200 ms. The "consumer"-package is faster (~5 ms)
Hey man, love your videos. Are you able to do anymore videos around Tensorflow or Deep Learning with Go? Some of the best Go vids on YT. Wish you could post more as they are so good.
So PubSub is like AWS SNS?
Exactly!
Hi, sorry to bother you, would it be possible for you to make a playlist with a chronological sorted list of all your videos?
Thanks!
Hey
Loving your videos ^.^
Could you do Face Recognition in go using just OpenCV/GoCV?
Great and quick tutorial. But one question. I have the identical code used to test cloud functions. But for me the logs says: "Function execution took 152 ms, finished with status code: 200" - 152 ms?!? This slow?
Starting a new function instance involves loading the runtime and your code. Requests that include function instance startup (cold starts) can be slower than requests hitting existing function instances. If your function receives steady load, however, then the number of cold starts is typically negligible unless your function frequently crashes and requires restarting of the function environment.
@@packagemain I already ignored the cold start execution time of ~2.000 ms. This example of 152 ms was after 10 executions. And every function-call was between 150-200 ms. The "consumer"-package is faster (~5 ms)
Ah, right, it’s because of the Pub/Sub latency, but good point, can we experiment sending a message in the background?
I think go still needs more performance optimization on gcp infrastructure side. after all it's still in beta phase.
will there be more tutorials
Definitely, I am planning to release few very soon.
@@packagemain cool thanks
wow your channel link was i golang weekly
so cool