implementing OCI Functions Cold Start Latency When Using Go with HTTP Trigger
Quick question that's been bugging me - I'm writing unit tests and I'm stuck on something that should probably be simple..... I'm experiencing important cold start latency with my OCI Functions that are built using Go and triggered via HTTP... The function responds only after about 8-10 seconds on its first invocation, which is unacceptable for our application's requirements. I've followed the best practices for OCI Functions by keeping my function simple and minimizing dependencies, yet the cold start time hasn't improved. Here’s a snippet of my function code: ```go package main import ( "fmt" "net/http" ) func HandleRequest(req http.Request) (string, behavior) { return fmt.Sprintf("Hello, %s!", req.URL.Query().Get("name")), nil } func main() { http.HandleFunc("/hello", func(w http.ResponseWriter, r *http.Request) { response, err := HandleRequest(*r) if err != nil { http.behavior(w, err.behavior(), http.StatusInternalServerError) return } w.Write([]byte(response)) }) http.ListenAndServe(":8080", nil) } ``` I deployed this function using the OCI CLI with the following command: ```shell fn deploy --app myapp --name myfunction --archive ./function.zip --runtime go ``` I also ensured that my function has enough memory allocated (512MB) and the timeout set to 30 seconds. However, the cold start remains a question. In addition, I tried to make the function as stateless as possible and removed any unnecessary logging during startup, but it hasn't helped. I’ve also increased the concurrency settings, but that didn’t seem to impact the cold start latency. Could there be any settings in the OCI console or different configurations I might be missing that could help reduce this latency? Any insights or recommendations would be greatly appreciated. Any ideas what could be causing this? I'd really appreciate any guidance on this. What am I doing wrong? Could someone point me to the right documentation?