okhttp application level OkHttpClient instance

Question

I was wondering if there will be any performance bottleneck or issues if I create one instance of OkHttpClient to serve my "entire android application". I.e.In my Application class, I create a static public variable that will contain a instance of OkHttpClient and whenever I need to do an http request I basically build a request object then use the created okhttpclient instance to fire the request.

Code to be like this

public class MyApplication extends Application {
    public static OkHttpClient httpClient;

    @Override
    public void onCreate() {
        super.onCreate();

        httpClient = new OkHttpClient();
    }

}

// Making request 1
Request request1 = new Request.Builder().url(ENDPOINT).build();
Response response = MyApplication.httpClient.newCall(request1).execute();

// Making request 2
Request request2 = new Request.Builder().url(ENDPOINT).build();
Response response = MyApplication.httpClient.newCall(request2).execute();

score 31 · Accepted Answer · edited Jan 25 '20 at 10:23

31

Using single instance is not a problem instead it is a common practice. You can check a similar app from github which uses dagger to make OkHttpClient singleton and injects it other modules.

And you can see in this discussion JakeWharton is also suggesting this kind of usage.

But it is better if you use a Singleton Pattern for this purpose.

edited Jan 25 '20 at 10:23

Marian Paździoch

8,813
10
58
103

answered Jun 17 '15 at 10:37

bhdrkn

6,244
5
35
42

1

Thanks @bhdrkn. I have seen both the discussion and the singleton style and I guess I will go for it. – Mutinda Boniface Jun 17 '15 at 11:15
Please note: single instance is not the same as singleton https://www.thekua.com/atwork/2009/01/singleton-vs-single-instance/. – Marian Paździoch May 04 '16 at 11:37
2

In case I have multiple domains I should use an okhttp instance per domain, right ? – Leandro Ocampo Aug 23 '17 at 18:54
5

Both links of this answer are out-dated. Please update the links or the answer. – Trinimon Mar 19 '18 at 09:21

score 14 · Answer 2 · answered Jan 30 '18 at 18:24

Apart from what @bhdrkn correctly suggests, to definitely confirm that a singleton instance of OkHttpClient is a correct way to go, an excerpt from documentation:

Source: https://square.github.io/okhttp/3.x/okhttp/okhttp3/OkHttpClient.html

OkHttpClients should be shared

OkHttp performs best when you create a single OkHttpClient instance and reuse it for all of your HTTP calls. This is because each client holds its own connection pool and thread pools. Reusing connections and threads reduces latency and saves memory. Conversely, creating a client for each request wastes resources on idle pools.

Refer to Javadoc (link above) to see correct ways of initializing OkHttpClient instance.

okhttp application level OkHttpClient instance

2 Answers2

Linked