I doubt go version has anything to do with this. What happens on that second OS (node1 not node-77) when you just run top in a shell? You could also rule out the go version by compiling on an OS with go version 1.15.7 and then using that binary on node1 to see if the output is different (I’m assuming you’re just using go run . here, not a binary).
Well, the version of go that is installed on node-77 has no bearing on how the binary performs, so that points to the command itself. Check your .bashrc for settings? I’m not super familiar with top or else I might have more specific troubleshooting steps there. Can you just specify the columns in the output?