Open webbben opened 10 months ago
For some reason go code execution seems to work fine now. it might be because we aren't putting them into their own small docker containers anymore, so it has access to all the resources (I think) that the fly.io containers give it.
It seems like executing go code takes significantly longer than other languages like Python. After some quick testing I think it's caused by the go build taking too long in the container. I guess building go code is taking a long time for some reason? Increasing the cpu threshold for a container seemed to slightly improve it, but not sure.
Anyway, considering trying to build the go code into executables before mounting it to the container, but should do a little more investigation first.