Application vs Network - Performance Analysis using Wireshark
Vložit
- čas přidán 17. 04. 2021
- In this video we'll be learning some tips on how to determine whether the network is slowing down an application, or if the server-side is to blame. We'll look at:
1 - Determining network RTT vs application response time
2 - Detecting packet loss in a capture
Additional Resources:
www.pico.net/kb/how-can-i-sim... - Simulating packet loss in linux using tc command - Věda a technologie
Thank you so much, your content is exclusive and it does help in many fields to troubleshoot. I have learned computer network fundamental in my university for 2 years but I don't know how to apply concepts in real life. And you are here and show me :D
Glad you are enjoying!
Thank you for sharing knowledge and experiance..
My pleasure
Very good and concise Explanation.
This is incredibly good and deserves more views
Great video , Waiting for more educational videos
thank you so much for this video , it really helped me to solve real production issue
Nice video , with what do you use grafana ? that is a nice dashboard .
Use grafana as front end for Prometheus to monitor home network and devices
Hi, very helpful.
do you stil broadcast videos somewhere ? Do you have tweeter or any other platform?
I haven’t had time for a few years now but will be posting more content soon
Helpful
Hello PP this is a really good session , but how do we identify application slowness then app uses UDP for communication. I have a Citrix workspace issue where udp is used to open workspace application and users are experiencing random slowness .
UDP protocols are much harder to analyze. If the protocol is plaintext (like SIP) you can inspect the packet contents themselves to see when the request hits the server vs the response. Additionally if the UDP packets have any sort of sequence identifier (like IPSEC) then you can spot whether any packets are lost in transit
Hey,
really like your Video. Is there any literature you can recommend regarding this topic?
TCP/IP Illustrated, Volume 1: The Protocols
That diagnostic is realy good for http but what if conversation is https or other?
The principle should remain true... What you need to remember is that 3 way handshake is indicative of network speed and responses from applications is indicative of application speed.
It’s similar but in HTTPS you don’t see HTTP requests in plaintext. You can still make some assumptions by looking at the TCP handshake whether the network itself is slow or lossy. There are ways to safely guess which encrypted packets represent HTTP requests but I’d have to make another video to explain how