1) n Goroutines or JobQueue

I have 1000 jobs that can be parallelized (http requests). Should I use 1000 Goroutines, or 10 Goroutines and a JobQueue? I'm assuming the first one would be extremely expensive or am I wrong?

2) reuse 1 http.Client or create new

Should I reuse a single instance of http.Client for all 1000 jobs? Does creating a new Client have a big overhead?

The problem is that worker plugins finish the jobs, so if I go with a single client, I'd have to burden the interface and pass the client to the workers from the master. I'd prefer not to unless creating multiple client has a big performance penalty.

Thanks!

Write the code, measure it, profile it :)

1) either approach will work, but goroutine-per-request is either unbounded in memory use, or you’ll need to write limiter code, which would be harder to understand than the job queue approach.

2) I don’t know the answer precisely, but this article seems to indicate that it’s ideal to reuse the same client as much as possible.