Java.net.SocketInputStream

Thread view:

Vikram - 10 Apr 2008 11:46 GMT

Hi,
I am using java.net.SocketInputStream to read the Http response.
For the first read, it takes around 2 minutes, but for the subsequent
reads, it is very fast ( in ms). Where could be the problem ?

Reply to this Message

Arne Vajhøj - 10 Apr 2008 23:48 GMT

> I am using java.net.SocketInputStream to read the Http response.
> For the first read, it takes around 2 minutes, but for the subsequent
> reads, it is very fast ( in ms). Where could be the problem ?

Impossible to say.

One possibility would be a very slow nameserver.

Arne

Reply to this Message

Viks - 11 Apr 2008 06:45 GMT

> > I am using java.net.SocketInputStream to read the Http response.
> > For the first read, it takes around 2 minutes, but for the subsequent
[quoted text clipped - 5 lines]
>
> Arne

Following can be reasons :

1. DNS resolution time
2. First Byte download time ( origin process time )

In most cases the first responses are heavy and involves connection
setup. The subsequent connections will reuse the connection hence are
faster i.e if your protocol is HTTP/1.1.

Viks

Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...