Hi,
Can you clarify if Go serverless functions fall under active CPU pricing?
This blog post suggests Fluid supports Node, Python, and Go.
But this documentation suggests Fluid Compute is only for Node, Python, and Edge.
Finally, running a few serverless Go functions of my own show no active cpu usage in the project Observability tab (memory and time to first byte are shown).
Hi,
It seems the blog post is incorrect. We support Fluid/Active CPU on edge, nodejs, and python. The docs are correct. We will update the blog post shortly.
Bummer, but thank you for clarifying.
Any chance adding support for the Go runtime is on the roadmap anytime soon? Or is there something too technically challenging about implementing for Go?
We don't have it on roadmap right now. But at some point we may consider it.