• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Network I/O Wait

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have a client server Java program that gets used at variety of customer locations. Sometime, I get complaints that the tool is running very slow and it turns out that it is due to the network I/O waits.

Is there a way, I could use some sorts of algorithm to determine if there is a network I/O waits and report on that so that a customer knows that it is not the tool but the network I/O waits?

I wrote this tool several years ago and it is still used by many. It is a small tool but useful to some.

How do I get to this? Any help is appreciated so that I can code this. Some code snippets would be very helpful.

It is a free tool and I do not get paid for the tool by anyone who is using this.

 
Rancher
Posts: 2759
32
Eclipse IDE Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Simple solution:- In your code, Just measure the time you are spending downloading data from server. This will give you a rough idea of how the network is performing. Use this measurement to compute a metric that you can show to the user. Like you can say average response time = XXX... or you can show a green/orange/red light on the UI

A little more complicated solution: -
Setup a timer that pings a server periodically, and checks how long it takes to get the response. This will help you get an idea of how the network is doing

Much more complicated solution:

Network throughput is really determined by 2 things latency and bandwidth. TO get an accurate idea of the throughput, you should be measuring both. Since, you don't want to invest too much time in a solution, you might want to stay away from this
 
Danger, 10,000 volts, very electic .... tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic