Two quick question about performance

<h1>1) n Goroutines <em>or</em> JobQueue</h1> <p>I have 1000 jobs that can be parallelized (http requests). Should I use 1000 Goroutines, or 10 Goroutines and a JobQueue? I&#39;m assuming the first one would be extremely expensive or am I wrong?</p> <h1>2) reuse 1 <code>http.Client</code> <em>or</em> create new</h1> <p>Should I reuse a single instance of <code>http.Client</code> for all 1000 jobs? Does creating a new Client have a big overhead?</p> <p>The problem is that worker <strong>plugins</strong> finish the jobs, so if I go with a single client, I&#39;d have to burden the interface and pass the client to the workers from the master. <em>I&#39;d prefer not to</em> unless creating multiple client has a big performance penalty.</p> <p>Thanks! :)</p> <hr/>**评论：**<br/><br/>recurrency: <pre><p>Write the code, measure it, profile it :)</p></pre>tmornini: <pre><p>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.</p> <p>2) I don’t know the answer precisely, but <a href="https://awmanoj.github.io/tech/2016/12/16/keep-alive-http-requests-in-golang/" rel="nofollow">this article</a> seems to indicate that it’s ideal to reuse the same client as much as possible.</p></pre>