CODEWITHSUNDEEP
javanetwork-programminghttpurlconnection
jerryc05
jerryc05

Reputation: 472

Java - url.openConnection() and httpsUrlConnection.connect() is running slow when first called

I found an interesting phenomenon when writing Java programs.

I had created 3 https connections to 3 different URLs, and I found that when I call url.openConnection() and httpsUrlConnection.connect() for the FIRST time, they took nearly 300ms and 1s to execute respectively, while during the second and third call, they took nearly 0ms.

Are there any reasons for these performance difference?

BTW, is there something I can do to improve the performance?

FYI, all of the three httpsURLConnection look like this (try-catch is not shown):

Url url = new URL("https://www.google.com");
Utils.logTime(logger);
HttpsURLConnection httpsURLConnection = (HttpsURLConnection) url.openConnection();
Utils.logTime(logger);
httpsURLConnection.setRequestMethod("GET");
httpsURLConnection.setConnectTimeout(5 * 1000);
httpsURLConnection.setReadTimeout(5 * 1000);
httpsURLConnection.setRequestProperty(Utils.ACCEPT, Utils.ACCEPT_ALL);
httpsURLConnection.setRequestProperty(Utils.ACCEPT_ENCODING, Utils.GZIP);
httpsURLConnection.setRequestProperty(Utils.USER_AGENT, Utils.MOZILLA);
Utils.addCookiesToConnection(httpsURLConnection, cookieMap);
Utils.logTime(logger);
httpsURLConnection.connect();
Utils.logTime(logger);

And as you may assume, Utils and cookieMap are a class and a HashMap created by myself, so they shall not be the focus of solution.

Any ideas? Thanks in advance.

Upvotes: 0

Views: 1243

Answers (1)

Gopu
Gopu

Reputation: 21

The reason for the time difference could be: the first time, socket connection needs to be established (from the source ip to the target ip and port). Once established, the same TCP connection could be reused. It's normal in network programming.

To improve efficiency and more control over the connection pooling, I would suggest considering Apache HttpClient

Upvotes: 1

Related Questions