Solved

System.currentTimeMillis() not giving correct results when measuring network latency

Posted on 2006-07-19
10
525 Views
Last Modified: 2013-11-15
Here is a fragment of my code:


// POP server logon code here

for(i=0;i<10;i++)
{
startTimer = System.currentTimeMillis();
os.write("list\r\n".getBytes());    // send LIST command to POP server
bytesRead = is.read(inputBuffer, 0, bufferSize);    // read data sent from POP server
stopTimer = System.currentTimeMillis();
}


I am basically try to measure the amount of time it takes to do a LIST and for the server to return the result. The first time the loop runs, I get a reasonable time difference (stopTimer - startTimer) about 150ms. However for all the other 9 loops I get 0.

Why is this the case?

0
Comment
Question by:rukiman
10 Comments
 
LVL 92

Expert Comment

by:objects
ID: 17143278
the accuracy depends on your os.
If the call takes less time than its accurate to then it could well show 0
0
 
LVL 23

Expert Comment

by:Ajay-Singh
ID: 17143624
> startTimer = System.currentTimeMillis();
> os.write("list\r\n".getBytes());    // send LIST command to POP server
> bytesRead = is.read(inputBuffer, 0, bufferSize);    // read data sent
> from POP server
> stopTimer = System.currentTimeMillis();

If there is any error, you might get false numbers. Try changing the code to:

startTimer = System.currentTimeMillis();
try {
    os.write("list\r\n".getBytes());    // send LIST command to POP server
    bytesRead = is.read(inputBuffer, 0, bufferSize);    // read data sent from POP server
}finally{
    stopTimer = System.currentTimeMillis();
}
0
 
LVL 26

Expert Comment

by:ksivananth
ID: 17143736
where you are calculating "stopTimer - startTimer"?

it should be immdtly after you get stopTimer or before you get startTimer!
0
 
LVL 30

Expert Comment

by:mayankeagle
ID: 17143975
Perhaps the first time it tries to write to the output-stream/ read from the input-stream it takes some time, and thereafter it manages to do it faster - I don't see this as an issue. The result you are getting is probably correct in the milli-second range.
0
 
LVL 35

Expert Comment

by:girionis
ID: 17144236
rukiman,
> Why is this the case?

Maybe the compiler optimizes some part of the byte code with a JIT compiler and it makes it run faster.
0
Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 12

Accepted Solution

by:
enachemc earned 125 total points
ID: 17144251
This might be a result from buffer size difference. Reading sockets is done in packets (a TCP/IP packet comes usualy with 1500 bytes). The first time you read, the information has to be read from the server, and if you do not read the entire buffer arrived, you will continue to read from the buffer, thus not involving any network time. You should do your analyses on big files and using bigger buffers (4K).
0
 
LVL 86

Expert Comment

by:CEHJ
ID: 17144295
Try changing that to

os.write("list\r\n".getBytes());    // send LIST command to POP server
os.flush();
0
 
LVL 4

Expert Comment

by:astorer
ID: 17145218
Option 1.  It could be that the server you are connecting to caches the information.  So, the first time around, it has to go and find the info before returning it taking 150ms.
Subsequently, it already has the information and can simply return it which is much quicker.  Zero is surprising though.

Option 2. It could be that the server has closed the socket.  So, when you do bytesRead = is.read(inputBuffer, 0, bufferSize); what is the value of bytesRead?  It could be -1 indicating that end of file has been reached.
You should always check for this.

In either case, you are not comparing like with like (i.e. the first request differes from subsequent).  The loop needs to go around the outer code that establishes the connection and gets the streams.
0
 
LVL 4

Expert Comment

by:orhanbaba
ID: 17152646
startTimer and stopTimer must be "long" not "integer"
0
 

Author Comment

by:rukiman
ID: 17269928
I found the problem....it was because I was out of sync and there was data already buffered to be read. I forgot that the server returned a response when I first connect to it and I wasn't reading this data.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Today companies are subjected to more-and-more data, and it won't stop any time soon.  But there are obvious opportunities for reducing data, particularly data duplicated among companies.
Healthcare organizations in the United States must adhere to the guidance of both the HIPAA (Health Insurance Portability and Accountability Act) and HITECH (Health Information Technology for Economic and Clinical Health Act) for securing and protec…
The viewer will learn how to implement Singleton Design Pattern in Java.
This tutorial will introduce the viewer to VisualVM for the Java platform application. This video explains an example program and covers the Overview, Monitor, and Heap Dump tabs.

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now