Application vs Network - Performance Analysis using Wireshark

Подписаться 17 тыс.

Просмотров 8 тыс.

50% 1

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/k... - Simulating packet loss in linux using tc command

Опубликовано:

27 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 21

@mohammadchavoshi5568 24 дня назад

Awesome explanation and simulation

@mysys-ib2lz 6 месяцев назад

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

@plaintextpackets 6 месяцев назад

Glad you are enjoying!

@supriyamishra1886 3 года назад

thank you so much for this video , it really helped me to solve real production issue

@upelister 5 месяцев назад

Thank you for sharing knowledge and experiance..

@plaintextpackets 5 месяцев назад

My pleasure

@nikhil9860 2 года назад

Great video , Waiting for more educational videos

@sitomiñanco-e4h 6 месяцев назад

Nice video , with what do you use grafana ? that is a nice dashboard .

@plaintextpackets 6 месяцев назад

Use grafana as front end for Prometheus to monitor home network and devices

@Chilaxmind 9 месяцев назад

Helpful

@sachin27506 11 месяцев назад

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 .

@plaintextpackets 11 месяцев назад

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

@yt_legend_papa Год назад

That diagnostic is realy good for http but what if conversation is https or other?

@hptc4400 Год назад

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.

@plaintextpackets Год назад

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