I am working on a project that uses a library which internally uses a lot of cgo. I have already built all my dependent modules and C code. During the first go run invocation things were slow, as expected, but later invocations quite fast. So all is good but I noticed something after the third invocation of go run command. The cache size grew by whopping 1MB. I got curious and immediately ran the go run command many times. Now the cache size grew a lot! What is happening here? Haven’t I already compiled all my required modules? So what is further adding to the cache size? Are my own packages being cached too every time I run the command? How do I stop this??