New server exclusively for dzone.com
Until now, dzone.com has lived on one of our servers that also hosts some other DeveloperZone/Javalobby services, but growth at dzone.com makes clear that it needs a home of its own.
We built a new server yesterday, and hopefully sometime today or this weekend we’ll be migrating dzone.com over to it. The new machine will run dzone.com and nothing else, and preliminary speed tests are indicating that it may perform much better than the dual-Xeon presently hosting the service.
We have adjusted DNS for www.dzone.com to have a very short TTL value in preparation for changing the IP address it resolves to. Still, you may notice a short period of hiccups while the DNS change propagates to other servers around the internet. It shouldn’t take more than a day or two for everything to settle down to normal after the changeover. TIA for you patience while it occurs.
BTW, we’d love to get some ping times to this new machine from around the world. Please post a comment if you would. The new machine’s address is 64.69.35.237 (cp8.javalobby.org) We’re also considering whether to move dzone.com from our Los Angeles data center to a facility located outside Washington, DC. If you want to post your ping times to 66.117.49.117 as well, then it might help us decide what to do. Thanks!
Subscribe to RSS Feed
September 22nd, 2006 at 8:31 am
Here are my results for the two machines. I am located in Cary, North Carolina running on Time-Warner Roadrunner cable service. The first set is the server in California, the second is the gateway to the East coast network facility (much closer to me, hence faster.)
Rick
————————
~ # ping
c 10 64.69.35.23764.69.35.237 ping statistics—-PING 64.69.35.237 (64.69.35.237): 56 data bytes
64 bytes from 64.69.35.237: icmp_seq=0 ttl=47 time=77.3 ms
64 bytes from 64.69.35.237: icmp_seq=1 ttl=47 time=79.0 ms
64 bytes from 64.69.35.237: icmp_seq=2 ttl=47 time=78.7 ms
64 bytes from 64.69.35.237: icmp_seq=3 ttl=47 time=81.9 ms
64 bytes from 64.69.35.237: icmp_seq=4 ttl=47 time=78.4 ms
64 bytes from 64.69.35.237: icmp_seq=5 ttl=47 time=78.1 ms
64 bytes from 64.69.35.237: icmp_seq=6 ttl=47 time=79.4 ms
64 bytes from 64.69.35.237: icmp_seq=7 ttl=47 time=78.2 ms
64 bytes from 64.69.35.237: icmp_seq=8 ttl=47 time=78.5 ms
64 bytes from 64.69.35.237: icmp_seq=9 ttl=47 time=78.6 ms
—
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 77.3/78.8/81.9 ms
~ # ping
c 10 66.117.49.11766.117.49.117 ping statistics—-PING 66.117.49.117 (66.117.49.117): 56 data bytes
64 bytes from 66.117.49.117: icmp_seq=0 ttl=115 time=24.5 ms
64 bytes from 66.117.49.117: icmp_seq=1 ttl=115 time=27.6 ms
64 bytes from 66.117.49.117: icmp_seq=2 ttl=115 time=27.2 ms
64 bytes from 66.117.49.117: icmp_seq=3 ttl=115 time=30.8 ms
64 bytes from 66.117.49.117: icmp_seq=4 ttl=115 time=22.8 ms
64 bytes from 66.117.49.117: icmp_seq=5 ttl=115 time=22.0 ms
64 bytes from 66.117.49.117: icmp_seq=6 ttl=115 time=22.5 ms
64 bytes from 66.117.49.117: icmp_seq=7 ttl=115 time=23.1 ms
64 bytes from 66.117.49.117: icmp_seq=8 ttl=115 time=23.5 ms
64 bytes from 66.117.49.117: icmp_seq=9 ttl=115 time=22.5 ms
—
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 22.0/24.6/30.8 ms
~ #
September 25th, 2006 at 10:40 pm
Hi there is there anyway to subscribe to the Rss feed of a particular Tag say “Web design”
September 26th, 2006 at 6:59 am
Sure, if you click to the “Browse by tag” page of your desired tag, then you should see the familiar orange RSS icon immediately to the left of the page title. That icon links to an RSS feed for that specific tag. In the case of the web design tag the RSS icon will link to the web design RSS feed.
Hope this helps. Please feel free to write us at support@dzone.com if you have any other questions.
September 26th, 2006 at 8:18 am
Here’s how it looks like from Israel:
Pinging 64.69.35.237 with 32 bytes of data:
Reply from 64.69.35.237: bytes=32 time=379ms TTL=53
Reply from 64.69.35.237: bytes=32 time=504ms TTL=53
Reply from 64.69.35.237: bytes=32 time=425ms TTL=53
Reply from 64.69.35.237: bytes=32 time=346ms TTL=53
Reply from 64.69.35.237: bytes=32 time=318ms TTL=53
Reply from 64.69.35.237: bytes=32 time=319ms TTL=53
Reply from 64.69.35.237: bytes=32 time=415ms TTL=53
Reply from 64.69.35.237: bytes=32 time=335ms TTL=53
Reply from 64.69.35.237: bytes=32 time=397ms TTL=53
Reply from 64.69.35.237: bytes=32 time=382ms TTL=53
Ping statistics for 64.69.35.237:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 318ms, Maximum = 504ms, Average = 382ms
September 26th, 2006 at 4:19 pm
330ms
353ms
359ms
From Hellas
September 27th, 2006 at 7:22 am
From Argentina….
Pinging 64.69.35.237 with 32 bytes of data:
Reply from 64.69.35.237: bytes=32 time=231ms TTL=48
Reply from 64.69.35.237: bytes=32 time=230ms TTL=48
Reply from 64.69.35.237: bytes=32 time=230ms TTL=48
Reply from 64.69.35.237: bytes=32 time=231ms TTL=48
Ping statistics for 64.69.35.237:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 230ms, Maximum = 231ms, Average = 230ms
———————————-
Pinging 66.117.49.117 with 32 bytes of data:
Reply from 66.117.49.117: bytes=32 time=169ms TTL=109
Reply from 66.117.49.117: bytes=32 time=168ms TTL=109
Reply from 66.117.49.117: bytes=32 time=172ms TTL=109
Reply from 66.117.49.117: bytes=32 time=170ms TTL=109
Ping statistics for 66.117.49.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 172ms, Average = 169ms
September 27th, 2006 at 12:47 pm
From Montreal, Canada
Pinging 64.69.35.237 with 32 bytes of data:
Reply from 64.69.35.237: bytes=32 time=88ms TTL=55
Reply from 64.69.35.237: bytes=32 time=86ms TTL=55
Reply from 64.69.35.237: bytes=32 time=92ms TTL=55
Reply from 64.69.35.237: bytes=32 time=99ms TTL=55
Reply from 64.69.35.237: bytes=32 time=87ms TTL=55
Reply from 64.69.35.237: bytes=32 time=87ms TTL=55
Reply from 64.69.35.237: bytes=32 time=95ms TTL=55
Reply from 64.69.35.237: bytes=32 time=86ms TTL=55
Reply from 64.69.35.237: bytes=32 time=87ms TTL=55
Reply from 64.69.35.237: bytes=32 time=180ms TTL=55
Ping statistics for 64.69.35.237:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 180ms, Average = 98ms
Pinging 66.117.49.117 with 32 bytes of data:
Reply from 66.117.49.117: bytes=32 time=37ms TTL=119
Reply from 66.117.49.117: bytes=32 time=31ms TTL=119
Reply from 66.117.49.117: bytes=32 time=31ms TTL=119
Reply from 66.117.49.117: bytes=32 time=36ms TTL=119
Reply from 66.117.49.117: bytes=32 time=46ms TTL=119
Reply from 66.117.49.117: bytes=32 time=71ms TTL=119
Reply from 66.117.49.117: bytes=32 time=32ms TTL=119
Reply from 66.117.49.117: bytes=32 time=52ms TTL=119
Reply from 66.117.49.117: bytes=32 time=55ms TTL=119
Reply from 66.117.49.117: bytes=32 time=32ms TTL=119
Ping statistics for 66.117.49.117:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 71ms, Average = 42ms
October 9th, 2006 at 4:42 pm
From Rorschacherberg, Switzerland
Pinging 66.117.49.117 with 32 bytes of data:
Reply from 66.117.49.117: bytes=32 time=110ms TTL=118
Reply from 66.117.49.117: bytes=32 time=108ms TTL=118
Reply from 66.117.49.117: bytes=32 time=109ms TTL=118
Reply from 66.117.49.117: bytes=32 time=109ms TTL=118
Ping statistics for 66.117.49.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 110ms, Average = 109ms
October 10th, 2006 at 3:10 pm
Here are the ping results of Belgium:
64.69.35.237
Minimum = 160 ms
Maximum = 164 ms
Average = 161 ms
66.117.49.117
Minimum = 104 ms
Maximum = 138 ms
Average = 117 ms
October 21st, 2006 at 5:41 pm
Here goes my pings, from Madrid (Spain).
PING 64.69.35.237 (64.69.35.237) 56(84) bytes of data.
64 bytes from 64.69.35.237: icmp_seq=1 ttl=49 time=228 ms
64 bytes from 64.69.35.237: icmp_seq=2 ttl=50 time=234 ms
64 bytes from 64.69.35.237: icmp_seq=3 ttl=50 time=238 ms
64 bytes from 64.69.35.237: icmp_seq=4 ttl=49 time=229 ms
64 bytes from 64.69.35.237: icmp_seq=5 ttl=50 time=238 ms
64 bytes from 64.69.35.237: icmp_seq=6 ttl=50 time=237 ms
64 bytes from 64.69.35.237: icmp_seq=7 ttl=49 time=230 ms
64 bytes from 64.69.35.237: icmp_seq=8 ttl=50 time=236 ms
64 bytes from 64.69.35.237: icmp_seq=9 ttl=50 time=236 ms
—- 64.69.35.237 ping statistics—
9 packets transmitted, 9 received, 0% packet loss, time 8030ms
rtt min/avg/max/mdev = 228.500/234.487/238.571/3.722 ms
PING 66.117.49.117 (66.117.49.117) 56(84) bytes of data.
64 bytes from 66.117.49.117: icmp_seq=1 ttl=111 time=205 ms
64 bytes from 66.117.49.117: icmp_seq=2 ttl=111 time=208 ms
64 bytes from 66.117.49.117: icmp_seq=3 ttl=110 time=202 ms
64 bytes from 66.117.49.117: icmp_seq=4 ttl=111 time=208 ms
64 bytes from 66.117.49.117: icmp_seq=5 ttl=111 time=210 ms
64 bytes from 66.117.49.117: icmp_seq=6 ttl=111 time=208 ms
64 bytes from 66.117.49.117: icmp_seq=7 ttl=111 time=210 ms
64 bytes from 66.117.49.117: icmp_seq=8 ttl=110 time=199 ms
— 66.117.49.117 ping statistics—-
8 packets transmitted, 8 received, 0% packet loss, time 7038ms
rtt min/avg/max/mdev = 199.850/206.861/210.801/3.584 ms
November 12th, 2006 at 1:48 pm
From London…
Pinging 64.69.35.237 with 32 bytes of data:
Reply from 64.69.35.237: bytes=32 time=154ms TTL=55
Reply from 64.69.35.237: bytes=32 time=152ms TTL=55
Reply from 64.69.35.237: bytes=32 time=152ms TTL=55
Reply from 64.69.35.237: bytes=32 time=154ms TTL=55
Ping statistics for 64.69.35.237:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 152ms, Maximum = 154ms, Average = 153ms
and….
Pinging 66.117.49.117 with 32 bytes of data:
Reply from 66.117.49.117: bytes=32 time=92ms TTL=120
Reply from 66.117.49.117: bytes=32 time=90ms TTL=120
Reply from 66.117.49.117: bytes=32 time=91ms TTL=120
Reply from 66.117.49.117: bytes=32 time=90ms TTL=120
Ping statistics for 66.117.49.117:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 92ms, Average = 90ms
December 20th, 2006 at 4:51 am
in iran,
Reply from 64.69.35.237: bytes=32 time=612ms TTL=47
Reply from 64.69.35.237: bytes=32 time=721ms TTL=48
Reply from 64.69.35.237: bytes=32 time=584ms TTL=47
Reply from 64.69.35.237: bytes=32 time=719ms TTL=46