Open URL Stream in Java

[PLUCKYHD]

is 1040ms to 1140ms a normally time just to open a url stream?

say I have u = new url(urladdress);

InputStream test = u.openStream();

the open stream call is taking anywhere from the above mentioned time which seems slow to me or am I crazy?

[GKusnick]

I haven't tried it, but I presume it's handshaking with the remote host to verify that the resource actually exists, so yeah, I'd expect it to take a few ping times to complete.

[stuckless]

plucky, i've seen connections (urls, databases, etc) take over a second to "connect", but it's rare. Now, if this is a url on your own network, then that is not normal. if it's a remote network, then it could latency (pings will show this) or it could a slow site (overloaded, etc).

Sometimes, if you are writing a piece of test code, that simply starts ups, opens a connection, and then shuts down, you will see very long times. Much of that time is java initially finding/loading classes that have not been accessed (ie, urlconnection, httpurlconnection, etc). So typically when I'm doing performance testing, as a test script, i will do all the work once... then I'll do it again, and take the timings of the second call. The reason, it that it will take all the initial object creation times out of the equation.

[PLUCKYHD]

Originally Posted by stuckless

plucky, i've seen connections (urls, databases, etc) take over a second to "connect", but it's rare. Now, if this is a url on your own network, then that is not normal. if it's a remote network, then it could latency (pings will show this) or it could a slow site (overloaded, etc).

Sometimes, if you are writing a piece of test code, that simply starts ups, opens a connection, and then shuts down, you will see very long times. Much of that time is java initially finding/loading classes that have not been accessed (ie, urlconnection, httpurlconnection, etc). So typically when I'm doing performance testing, as a test script, i will do all the work once... then I'll do it again, and take the timings of the second call. The reason, it that it will take all the initial object creation times out of the equation.

Yeah repeated runs yield maybe 100ms to 200ms better. Guess that is just the name of the game was hoping for better results but I will live with it