Question: is this an automated summary or are you doing these summaries yourself manually?
On topic, it seems odd that a Python process that would take 3 minutes to scan nodes could be reduced to a go script that takes under 1 second. Perhaps this is entirely due to going from serial to parallel, but the timeout thing that he mentioned sounds like an error in the Python code rather than a language problem. And I say this as someone who uses/enjoys go.
Indeed.. I would have liked to hear what took the Python script 3x longer. The longest part I would assume would be the network requests themselves which is inherent regardless of language.
Sounds like it the execution time required to processing the vast amounts of data produced. go is quite likely to beat python in compute bound or data crunching tasks.
Go is definitely faster than Python for those types of tasks, however I'm suspicious of it being that much faster. I've crunched massive data sets in Python and as long as you're aware of its limitations, you can make things pretty zippy.
On topic, it seems odd that a Python process that would take 3 minutes to scan nodes could be reduced to a go script that takes under 1 second. Perhaps this is entirely due to going from serial to parallel, but the timeout thing that he mentioned sounds like an error in the Python code rather than a language problem. And I say this as someone who uses/enjoys go.