Should I use one HttpClient instance per request or one to handle all my requests?

Question

I'm creating a client for Rest API and I'm using the HttpClient class. My question is: should I use just one instance to handle all my requests? or should I create a new instance per request? Like:

using (var client = new HttpClient()) {
  ...
}

Is there any recommended practice?

good explanation on when to reuse and when to use new HttpClient http://stackoverflow.com/questions/22560971/what-is-the-overhead-of-creating-a-new-httpclient-per-call-in-a-webapi-client — Aaron Hoffman, Jul 04 '15 at 13:58

score 8 · Accepted Answer · answered Jan 29 '13 at 20:12

8

You should try to reuse HttpClient instances as much as possible. The only reason to create a new instance is if you want to configure it differently.

answered Jan 29 '13 at 20:12

Youssef Moussaoui

12,187
2
41
37

Thanks!. Do you have any source? – dmorganb Jan 29 '13 at 20:16
6

I'm a developer on the WebAPI team. I double-checked for you with the right person. : ) – Youssef Moussaoui Jan 29 '13 at 22:58
How about a link to an example that shows how best to implement this advice? – flipdoubt Aug 18 '16 at 12:22
1

This is an interesting article which confirms Youssef's answer: http://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/ – Frederik Gheysels Aug 31 '16 at 08:37

Should I use one HttpClient instance per request or one to handle all my requests?

1 Answers1