Why is my Initial call in RestSharp really slow? but others after are very fast

Question

I am making calls to a WEB API using RESTSHARP and they work fine. However, the Initial call to the API (regardless of what call it is) can sometimes take up to 10 seconds to get a response. Every other call after that is really quick. Does anyone know a way around this?

I am running a WPF 4.0 application

code:

var client = new RestClient(apiAddress);
var request = new RestRequest(Method.GET);

IRestResponse response = client.Execute(request);

That's ususally some firewall or other network issue. Not your code. — H H, Sep 04 '12 at 09:00
First call from a fresh client, or first call to a fresh server? — Jon Skeet, Sep 04 '12 at 09:05
I would suggest it is possibly the service starting, or resuming from a rest state. — podiluska, Sep 04 '12 at 09:16
I've just had this problem too. In our case the problem was IIS had put the pool/site to sleep and it took a while (23.8 seconds) to wake up. — Simon Hughes, Sep 15 '17 at 15:52

score 13 · Accepted Answer · edited Sep 17 '12 at 16:45

13

It's most likely the network settings causing this problem. I recently had the same issue and it turned out that when using HttpWebRequest or RestSharp it was trying some auto configuration to look for a proxy server.

Open the network settings in Internet Explorer and disable auto configuration for the local network. In my case this resolved the delay for the first request in RestSharp as well.

edited Sep 17 '12 at 16:45

Servy

202,030
26
332
449

answered Sep 17 '12 at 14:23

skrause

989
1
9
14

1

This did fix the problem Servy. I have marked this as correct, however it wont be any use to me as I am developing a commercial application which is to be installed on multiple computers and I cant force users to disable this option. Thanks though for clarifying. – Neil Hobson Oct 05 '12 at 15:23
You can also do this: http://stackoverflow.com/questions/2519655/httpwebrequest-is-extremely-slow – christo8989 Sep 16 '15 at 21:58

score 5 · Answer 2 · answered Dec 08 '16 at 14:08

I had attempted @skrause's answer, but it wasn't work for me. I spend much time, and finaly I solved it. This my sulotion.

public class SimpleWebProxy : IWebProxy
{
    public ICredentials Credentials { get; set; }

    public Uri GetProxy(Uri destination)
    {
        return destination;
    }

    public bool IsBypassed(Uri host)
    {
        // if return true, service will be very slow.
        return false;
    }

    private static SimpleWebProxy defaultProxy = new SimpleWebProxy();
    public static SimpleWebProxy Default
    {
        get
        {
            return defaultProxy;
        }
    }
}

var client = new RestClient();
client.Proxy = SimpleWebProxy.Default;

score 2 · Answer 3 · answered Jun 03 '16 at 13:49

2

Tried to get rid of the auto configuration to look for a proxy server with this

System.Net.WebRequest.DefaultWebProxy = null;

answered Jun 03 '16 at 13:49

CAA

23
4

score 0 · Answer 4 · answered Jan 22 '14 at 11:21

0

If You use winforms etc. in app.config after connectionstrings:

<system.net>
  <defaultProxy enabled="true">
    <proxy usesystemdefault="True"/>
  </defaultProxy>
</system.net>

answered Jan 22 '14 at 11:21

Inspector

11
1

Hi, i used this code configuration and it's now work "never work " – Osama khodroj May 23 '16 at 09:10
1

@Osamakhodrog Did it work or not? What signifies with "never work"? – hiFI Sep 21 '16 at 08:22
It worked for me, I think the key statement is "winforms" although in my case it was a console app. It's probably not the same for a web server. – Jay13 Oct 27 '17 at 21:34
for a website its the same, however app.config is called web.config – magallanes Dec 22 '17 at 19:40

Why is my Initial call in RestSharp really slow? but others after are very fast

4 Answers4

Linked