Web sunuculara latency olcumu

Zaman zaman web sunucularımıza performans testleri yaparak kapasitlerini ölçüyoruz. Performans testleri esnasında web sunucuların yük durumu, hizmet kalitesi ve dışardan bağlanan kullanıcılara yaşattığı latency değerlerini ölçmek gerekiyor. Latency harici diğer değerler sistem üzerinden snmp vs ile alinabiliyor, latency ölçümü için networkun dışından birilerinden siteye girmelerini isteyip yavaşlık var mı sorusu sayısal değerlerden uzak olduğu için pek işime yaramıyordu. Kısa bir araştırmayla bu konuda kullanılabilecek iki araç buldum ve inceledim. Araçlardan biri http_ping diğeri de daha kapsamlı testlerde kullanılabilecek bir araç olan echoping

Alternatif araç önerileriniz varsa yorumlarınızla zenginleştirebilirsiniz.

Http_ping ile latency testleri

# http_ping -count  5 -interval 5  http://www.turkcell.com.tr

219 bytes from http://www.turkcell.com.tr: 24.088 ms (11.618c/12.458r/0.012d)
219 bytes from http://www.turkcell.com.tr: 23.424 ms (10.788c/12.621r/0.015d)
219 bytes from http://www.turkcell.com.tr: 17.003 ms (8.413c/8.577r/0.013d)
219 bytes from http://www.turkcell.com.tr: 20.625 ms (9.113c/11.501r/0.011d)

219 bytes from http://www.turkcell.com.tr: 20.398 ms (8.221c/12.165r/0.012d)

— http://www.turkcell.com.tr http_ping statistics —
5 fetches started, 5 completed (100%), 0 failures (0%), 0 timeouts (0%)
total    min/avg/max = 17.003/21.1076/24.088 ms
connect  min/avg/max = 8.221/9.6306/11.618 ms
response min/avg/max = 8.577/11.4644/12.621 ms
data     min/avg/max = 0.011/0.0126/0.015 ms

Echoping ile latency testleri

[[email protected] ~]# echoping -v  -n 5 -w 3 -R -D  -h /anasayfa www.turkcell.com.tr

This is echoping, version 6.0.0.

Trying to connect to internet address 212.252.168.225 80 to transmit 103 bytes…
Trying to send 256 bytes to internet address 212.252.168.225…
Connected…
TCP Latency: 0.005898 seconds
Sent (103 bytes)…
Application Latency: 0.044271 seconds
12781 bytes read from server.
Elapsed time: 0.059465 seconds
Trying to connect to internet address 212.252.168.225 80 to transmit 103 bytes…
Trying to send 256 bytes to internet address 212.252.168.225…
Connected…
TCP Latency: 0.004449 seconds
Sent (103 bytes)…
Application Latency: 0.050749 seconds
12779 bytes read from server.
Elapsed time: 0.068128 seconds
Trying to connect to internet address 212.252.168.225 80 to transmit 103 bytes…
Trying to send 256 bytes to internet address 212.252.168.225…
Connected…
TCP Latency: 0.013045 seconds
Sent (103 bytes)…
Application Latency: 0.042985 seconds
12781 bytes read from server.
Elapsed time: 0.060604 seconds
Trying to connect to internet address 212.252.168.225 80 to transmit 103 bytes…
Trying to send 256 bytes to internet address 212.252.168.225…
Connected…
TCP Latency: 0.004867 seconds
Sent (103 bytes)…
Application Latency: 0.044789 seconds
12781 bytes read from server.
Elapsed time: 0.053972 seconds
Trying to connect to internet address 212.252.168.225 80 to transmit 103 bytes…
Trying to send 256 bytes to internet address 212.252.168.225…
Connected…
TCP Latency: 0.003864 seconds
Sent (103 bytes)…
Application Latency: 0.056953 seconds
12779 bytes read from server.
Elapsed time: 0.065896 seconds

Minimum time: 0.053972 seconds (4743 bytes per sec.)
Maximum time: 0.068128 seconds (3758 bytes per sec.)
Average time: 0.061613 seconds (4155 bytes per sec.)
Standard deviation: 0.031128
Median time: 0.044271 seconds (5783 bytes per sec.)

http_ping’in detay kullanımı için man http_ping komutu kullanılabilir.

man http_ping

http_ping(1)                                                      http_ping(1)

NAME
http_ping – measure HTTP latency

SYNOPSIS
http_ping [-count n] [-interval n] [-quiet] [-proxy host:port] url

DESCRIPTION
http_ping  runs  an  HTTP  fetch  every few seconds, timing how long it
takes.

Sample run:
% http_ping http://www.example.com/
7816 bytes from http://www.example.com/: 246.602 ms (9.923c/23.074r/213.605d)
7816 bytes from http://www.example.com/: 189.997 ms (11.619c/22.971r/155.407d)
7816 bytes from http://www.example.com/: 190.463 ms (8.994c/25.091r/156.378d)
7816 bytes from http://www.example.com/: 190.07 ms (9.234c/23.9r/156.936d)
7816 bytes from http://www.example.com/: 190.706 ms (10.142c/46.579r/133.985d)
^C
— http://www.example.com/ http_ping statistics —
5 fetches started, 5 completed (100%), 0 failures (0%), 0 timeouts (0%)
total    min/avg/max = 189.997/201.568/246.602 ms
connect  min/avg/max = 8.994/9.9824/11.619 ms
response min/avg/max = 22.971/28.323/46.579 ms
data     min/avg/max = 133.985/163.262/213.605 ms

OPTIONS
-count Stop after  the  specified  number  of  fetches.   Without  this
option, http_ping will continue until interrupted.

-interval
Wait  the  specified  number  of  seconds  between fetches.  The
default is five seconds.

-quiet Only display the summary info at the end.

-proxy Specifies a proxy host and port to use.

SEE ALSO
http_load(1), http_get(1), ping(8)

AUTHOR
Copyright (C) 1998,1999,2001,2002 by Jef Poskanzer <[email protected]>.
All rights reserved.

This entry was posted in Misc, Network Security, Network Tools, Web Security. Bookmark the permalink.

2 Responses to Web sunuculara latency olcumu

  1. Ahmet T says:

    Asagidaki link de bu is icin kullanabileceginiz tool lar var. Hem open source hem trial olarak deneyebileceginiz programlar mevcut.

    http://softwareqatest.com/qatweb1.html

  2. Suat Çelik says:

    Eski Mercury Interactive şimdi Hp altında “HP LoadRunner software” i var,bi dönemler , accelaration cihazları testi için kullanırdık…Oldukça detaylı bir tool…

Leave a Reply

Your email address will not be published. Required fields are marked *

one × 1 =