cest moderatorum (a osmerovi zejmena! :laugh: )
poslys, osmero, az budes nejak mluvit s kolegou Cermakem, ze ho prosim, jestli by bylo mozny, aby se spojil sam se sebou v Zippy Data, a za Zippy Data poprosil Simply Transit Ltd., jestli by se nemohli podivat se na nastaveni memory cache na sevreru, kterej reversuje IP 94.x.x.x ??
prijde mi, ze to nemaj nastaveny prilis koser, protoze serverova odezva je v ruznych dennich casech neskutecne rozjebana. navic i ping vypada nejak podivne (coz ovsem nemusi byt nutne chyba jen na strane koncoveho serveru, sve tomu dava i slavny Sir Richard Branson...):
PING 94.76.254.89 (94.76.254.89) 56(84) bytes of data.
64 bytes from 94.76.254.89: icmp_req=1 ttl=52 time=19.4 ms
64 bytes from 94.76.254.89: icmp_req=2 ttl=52 time=35.7 ms
64 bytes from 94.76.254.89: icmp_req=3 ttl=52 time=20.9 ms
64 bytes from 94.76.254.89: icmp_req=4 ttl=52 time=19.7 ms
64 bytes from 94.76.254.89: icmp_req=5 ttl=52 time=20.9 ms
64 bytes from 94.76.254.89: icmp_req=7 ttl=52 time=39.4 ms
64 bytes from 94.76.254.89: icmp_req=8 ttl=52 time=23.0 ms
64 bytes from 94.76.254.89: icmp_req=9 ttl=52 time=19.0 ms
64 bytes from 94.76.254.89: icmp_req=10 ttl=52 time=20.7 ms
64 bytes from 94.76.254.89: icmp_req=11 ttl=52 time=30.0 ms
64 bytes from 94.76.254.89: icmp_req=12 ttl=52 time=20.1 ms
64 bytes from 94.76.254.89: icmp_req=13 ttl=52 time=20.7 ms
64 bytes from 94.76.254.89: icmp_req=14 ttl=52 time=19.5 ms
64 bytes from 94.76.254.89: icmp_req=15 ttl=52 time=30.2 ms
64 bytes from 94.76.254.89: icmp_req=16 ttl=52 time=22.0 ms
64 bytes from 94.76.254.89: icmp_req=17 ttl=52 time=37.0 ms
64 bytes from 94.76.254.89: icmp_req=18 ttl=52 time=21.4 ms
64 bytes from 94.76.254.89: icmp_req=19 ttl=52 time=19.9 ms
64 bytes from 94.76.254.89: icmp_req=20 ttl=52 time=18.8 ms
64 bytes from 94.76.254.89: icmp_req=21 ttl=52 time=27.8 ms
64 bytes from 94.76.254.89: icmp_req=22 ttl=52 time=37.5 ms
---
ta odezva fakt strasne lita, pricemz na mym domacim serveru se ping jeste docela drzi:
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_req=1 ttl=63 time=2.87 ms
64 bytes from 10.0.0.1: icmp_req=2 ttl=63 time=1.51 ms
64 bytes from 10.0.0.1: icmp_req=3 ttl=63 time=1.49 ms
64 bytes from 10.0.0.1: icmp_req=4 ttl=63 time=1.48 ms
64 bytes from 10.0.0.1: icmp_req=5 ttl=63 time=1.51 ms
64 bytes from 10.0.0.1: icmp_req=6 ttl=63 time=3.19 ms
64 bytes from 10.0.0.1: icmp_req=7 ttl=63 time=1.50 ms
64 bytes from 10.0.0.1: icmp_req=8 ttl=63 time=1.75 ms
64 bytes from 10.0.0.1: icmp_req=9 ttl=63 time=1.51 ms
64 bytes from 10.0.0.1: icmp_req=10 ttl=63 time=1.46 ms
64 bytes from 10.0.0.1: icmp_req=11 ttl=63 time=1.49 ms
64 bytes from 10.0.0.1: icmp_req=12 ttl=63 time=1.48 ms
64 bytes from 10.0.0.1: icmp_req=13 ttl=63 time=1.80 ms
64 bytes from 10.0.0.1: icmp_req=14 ttl=63 time=1.69 ms
64 bytes from 10.0.0.1: icmp_req=15 ttl=63 time=1.49 ms
64 bytes from 10.0.0.1: icmp_req=16 ttl=63 time=1.49 ms
64 bytes from 10.0.0.1: icmp_req=17 ttl=63 time=1.52 ms
64 bytes from 10.0.0.1: icmp_req=18 ttl=63 time=1.43 ms
64 bytes from 10.0.0.1: icmp_req=19 ttl=63 time=1.51 ms
64 bytes from 10.0.0.1: icmp_req=20 ttl=63 time=1.58 ms
64 bytes from 10.0.0.1: icmp_req=21 ttl=63 time=1.50 ms
---
a dokonce i prvni router na trase, kterej predava, se drzi docela statecne:
roman@IBM-T40LINUX ~ $ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=64 time=1.22 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=64 time=1.45 ms
64 bytes from 192.168.2.1: icmp_req=3 ttl=64 time=1.55 ms
64 bytes from 192.168.2.1: icmp_req=4 ttl=64 time=0.876 ms
64 bytes from 192.168.2.1: icmp_req=5 ttl=64 time=0.856 ms
64 bytes from 192.168.2.1: icmp_req=6 ttl=64 time=1.10 ms
64 bytes from 192.168.2.1: icmp_req=7 ttl=64 time=1.21 ms
64 bytes from 192.168.2.1: icmp_req=8 ttl=64 time=0.817 ms
64 bytes from 192.168.2.1: icmp_req=9 ttl=64 time=0.880 ms
64 bytes from 192.168.2.1: icmp_req=10 ttl=64 time=0.880 ms
64 bytes from 192.168.2.1: icmp_req=11 ttl=64 time=0.911 ms
64 bytes from 192.168.2.1: icmp_req=12 ttl=64 time=0.851 ms
64 bytes from 192.168.2.1: icmp_req=13 ttl=64 time=0.826 ms
64 bytes from 192.168.2.1: icmp_req=14 ttl=64 time=0.865 ms
64 bytes from 192.168.2.1: icmp_req=15 ttl=64 time=1.15 ms
64 bytes from 192.168.2.1: icmp_req=16 ttl=64 time=1.25 ms
---
ale pak uz zacina drama:
roman@IBM-T40LINUX ~ $ traceroute www.pohyby.co.uk
traceroute to www.pohyby.co.uk (94.76.254.89), 30 hops max, 60 byte packets
1 . (192.168.2.1) 1.777 ms 3.550 ms 3.599 ms
2 10.0.0.1 (10.0.0.1) 3.699 ms 5.527 ms 6.375 ms
3 10.100.188.1 (10.100.188.1) 16.209 ms 20.282 ms
[b]32.441 ms[/b]edit: to je Branson a slavnej Virgin 4 pool-cam-1b-ge99.network.virginmedia.net (80.5.168.173) 35.807 ms 39.635 ms 39.749 ms 5 sotn-core-1b-ge-112-0.network.virginmedia.net (80.4.225.137) 40.358 ms 41.076 ms 44.394 ms 6 glfd-bb-1b-ae3-0.network.virginmedia.net (212.43.163.153) 46.524 ms 13.341 ms 13.526 ms 7 nrth-bb-1a-as5-0.network.virginmedia.net (212.43.163.182) 31.374 ms 31.532 ms 31.607 ms 8 nrth-bb-1b-ae0-0.network.virginmedia.net (62.253.185.118) 24.253 ms 45.838 ms 50.211 ms
[b] 9 nrth-tmr-2-ae6-0.network.virginmedia.net (213.105.159.34) 52.094 ms 51.848 ms 54.285 ms 10 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 55.743 ms 61.372 ms 65.648 ms 11 the-linx.as29550.net (195.66.224.223) 65.779 ms 69.648 ms 69.674 ms 12 pri.the-mka_450.as29550.net (94.76.244.22) 69.241 ms 59.731 ms 24.122 ms[/b]13 213-229-71-160.static.as29550.net (213.229.71.160) 24.756 ms 24.829 ms 21.062 ms 14 pohyby.co.uk (94.76.254.89) 23.927 ms 25.467 ms 25.549 ms roman@IBM-T40LINUX ~ $ --- je ale fakt, ze lehce se v tom placaj i hosi z BlueConnex MK Ltd., ktery maj zarez na odezve 59 ms, to uz je sila. ale pak uz je v tom jen Simply Transit Ltd... takze se v tom veze nejen Simply Transit, jsou v tom namoceny samozrejme i Virgin a BlueConnex... nestalo by za uvahu zmenit hosting nekam, kde neni tak sileny trasovani, a kde si umi poladit servery a zoptimalizovat memory cache?? a dost mozna by pomohlo vykostit Kunenu a nasadit neco mene rozprasenyho (Kunena je obecne vnimana jako nejhorsi mozna nastavba k Joomla...) ? a at to nebere ve zlem, jsou to jen postrehy, ktery nejsou upeceny ted a tady - pomalou odezvu pohybu.co.uk uz sleduju asi pul roku... dikes!
- Stránka :
- 1
K tomuto dotazu nejsou zatím žádné odpovědi.