Consider this code in a php file on my VPS server:
<?php $url = 'http://www.google.com'; $ch = curl_init(); curl_setopt($ch, CURLOPT_URL, $url); curl_setopt($ch, CURLOPT_USERAGENT, "Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1" ); curl_setopt($ch, CURLOPT_HEADER, 0); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); $content = curl_exec($ch); $ci = curl_getinfo($ch); curl_close($ch); var_dump($ci); ?>
returns this
array(22) { ["url"]=> string(21) "http://www.google.com" ["content_type"]=> string(24) "text/html; charset=UTF-8" ["http_code"]=> int(200) ["header_size"]=> int(2055) ["request_size"]=> int(147) ["filetime"]=> int(-1) ["ssl_verify_result"]=> int(0) ["redirect_count"]=> int(0) ["total_time"]=> float(50.095466) ["namelookup_time"]=> float(0.001114) ["connect_time"]=> float(50.019724) ["pretransfer_time"]=> float(50.019825) ["size_upload"]=> float(0) ["size_download"]=> float(23156) ["speed_download"]=> float(462) ["speed_upload"]=> float(0) ["download_content_length"]=> float(-1) ["upload_content_length"]=> float(0) ["starttransfer_time"]=> float(50.070702) ["redirect_time"]=> float(0) ["certinfo"]=> array(0) { } ["redirect_url"]=> string(0) "" }
After testing several times, "connect_time" is constantly at around 50 seconds. I believe that it should be 10 times faster, if not at around 1 second or less.
I am not aware of the server configuration, but I was told that my server processor or RAM might be to blame. I used the top command line to display the following, which seems good to me:
Tasks: 80 in total, 1 working, 79 sleeping, 0 stopped, 0 zombies
CPU (s): 0.0% us, 0.0% sy, 0.0% ni, 100.0% id, 0.0% wa, 0.0% hi, 0.0% si, 0.0%
Mem: 2097152k total, used 1273128k, 824024k free, 0k buffers
Exchange: 0k total, 0k used, 0k free, 0k cache
I am wondering what could be the source of this problem?
EDIT: ADDITIONAL INFORMATION
ping Result www.google.com. It seemed that this could continue, so I stopped the team after the 195th line
PING www.l.google.com (74.125.224.178) 56 (84) bytes of data.
64 bytes from lax02s01-in-f18.1e100.net (74.125.224.178): icmp_seq = 1 ttl = 56 times = 12.0 ms
64 bytes from lax02s01-in-f18.1e100.net (74.125.224.178): icmp_seq = 2 ttl = 56 times = 12.1 ms
64 bytes from lax02s01-in-f18.1e100.net (74.125.224.178): icmp_seq = 3 ttl = 56 times = 11.9 ms
...
64 bytes from lax02s01-in-f18.1e100.net (74.125.224.178): icmp_seq = 194 ttl = 56 times = 11.9 ms
64 bytes from lax02s01-in-f18.1e100.net (74.125.224.178): icmp_seq = 195 ttl = 56 times = 11.9 ms
--- www.l.google.com ping statistics --- 195 packets transmitted, 194 received, 0% packet loss, time 194711ms
Result of traceroute wwww.google.com
traceroute at www.google.com (74.125.224.180), maximum 30 jumps, 60 byte packets
1 ip --- * -. ip.secureserver.net (. * ..) 0.585 ms 0.642 ms 0.778 ms
2 be10.trmd0215-01.ars.mgmt.phx3.gdg (208.109.112.126) 0.599 ms 0.777 ms 0.833 ms
3 ip-97-74-253-122.ip.secureserver.net (97.74.253.122) 11.840 ms 12.119 ms 12.275 ms
4 ip-97-74-253-122.ip.secureserver.net (97.74.253.122) 12.389 ms 12.482 ms 12.600 ms
5 PR01.LAX03.google.com (206.223.123.21) 11.739 ms 11.709 ms 11.707 ms
6 209.85.248.185 (209.85.248.185) 11.986 ms 11.797 ms 11.781 ms
7 72.14.236.11 (72.14.236.11) 12.606 ms 12.363 ms 12.328 ms
8 lax02s01-in-f20.1e100.net (74.125.224.180) 11.774 ms 11.864 ms 11.842 ms