Trying to isolate if the application is sluggish or if it's a network congestion issue



  • I'm trying to nail down why our application is sluggish at certain times. The application sometimes is zippy almost instantaneous and other times it is slow as molasses. The application is run on a server with clients in our department. It is only intranet communication. During the day after 10 am, it becomes super slow (until after 4 pm).

    I am having the problem where the developers are pointing to our I.T. and our I.T. pointing fingers to our developers. Is there any way that a general user like me can isolate which is the major contributing factor? The only tool I am aware of using is the ping. Is there any other simple way to help give a clearer picture? That is the challenge, using tools that easily available on most computers.



  • A divide and conquer approach usually gives good results, you focus on a specific module (or a collection of modules) monitoring it or if possible replacing it with something else.

    When you find a suspicious module try to further sub dividing it until you find the root cause.

    Note that this is usually an exploratory and iterative approach, you try something that in return will hint what should be the next step.

    The main downside of such an approach is in cases where the cause is not a single component but a chain of failures, or cases where you found the trigger to the problem but not the root cause.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2