title: Should RestClient be singleton or new for every request
body: <p>ASP.Net <code>HttpClient</code> is disposable, and a lot of articles say you should use the singleton pattern to use it because of the performance. But when I see the <code>RestClient</code> it can't be disposed, and in the <a href="https://github.com/restsharp/RestSharp/wiki/Recommended-Usage" rel="noreferrer">Recommended-Usage</a> page the sample will <code>new</code> the <code>RestClient</code> every time. Should I use singleton pattern for <code>RestClient</code> or should I <code>new</code> it every time? If I <code>new</code> it every time will there be any performance concern?</p>
  <p><a href="https://github.com/restsharp/RestSharp" rel="noreferrer">RestSharp GitHub</a></p>
  <p>Some references:</p>
  <p><a href="https://stackoverflow.com/questions/15705092/do-httpclient-and-httpclienthandler-have-to-be-disposed?utm_medium=organic&amp;utm_source=google_rich_qa&amp;utm_campaign=google_rich_qa">Do HttpClient and HttpClientHandler have to be disposed
  </a></p>
  <p><a href="https://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/" rel="noreferrer">YOU'RE USING HTTPCLIENT WRONG AND IT IS DESTABILIZING YOUR SOFTWARE</a></p>