Slow performance

June 9, 2010, 9:35 p.m.
I want you guys to improve the performance of the server running this website because it is very slow.
June 9, 2010, 10 p.m.
errr not really.
June 10, 2010, 12:30 a.m.
Never noticed that it's slow, check your net connection.
June 10, 2010, 2:14 a.m.
post you ping to the site. I know for a fact its more likely your connection and not this server.
June 10, 2010, 3:02 a.m.
Pinging nfscars.net [207.88.48.254] with 32 bytes of data:
Reply from 207.88.48.254: bytes=32 time=132ms TTL=110
Reply from 207.88.48.254: bytes=32 time=126ms TTL=110
Reply from 207.88.48.254: bytes=32 time=126ms TTL=110
Reply from 207.88.48.254: bytes=32 time=132ms TTL=110

Ping statistics for 207.88.48.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 132ms, Average = 129ms

No problems here. Check your net, OP.
June 10, 2010, 3:12 a.m.
Ping http://www.nfscars.net [89.246.64.39] mit 32 Bytes Daten:

Antwort von 89.246.64.39: Bytes=32 Zeit=14ms TTL=58
Antwort von 89.246.64.39: Bytes=32 Zeit=13ms TTL=58
Antwort von 89.246.64.39: Bytes=32 Zeit=13ms TTL=58
Antwort von 89.246.64.39: Bytes=32 Zeit=14ms TTL=58

Ping-Statistik für 89.246.64.39:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 13ms, Maximum = 14ms, Mittelwert = 13ms

As fast as always.

Just as prevention: In case you dont know how to ping; press windows key + r , enter "cmd", hit enter, then type "ping http://www.nfscars.net" and hit enter. Then copy your result and paste it here.
June 10, 2010, 3:19 a.m.
Pinging nfscars.net [207.88.48.254] with 32 bytes of data:
Reply from 207.88.48.254: bytes=32 time=251ms TTL=116
Reply from 207.88.48.254: bytes=32 time=295ms TTL=116
Reply from 207.88.48.254: bytes=32 time=248ms TTL=116
Reply from 207.88.48.254: bytes=32 time=271ms TTL=116

Ping statistics for –––:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 248ms, Maximum = 295ms, Average = 266ms
July 19, 2010, 2:01 p.m.
F.R,

Can you try pinging the site again and post the results? You should hopefully see an improvement but it all depends where you are located.

My results but I am very close to the servers:

Pinging nfscars.net [67.202.114.134] with 32 bytes of data:
Reply from 67.202.114.134: bytes=32 time=12ms TTL=120
Reply from 67.202.114.134: bytes=32 time=12ms TTL=120
Reply from 67.202.114.134: bytes=32 time=13ms TTL=120
Reply from 67.202.114.134: bytes=32 time=12ms TTL=120

Ping statistics for 67.202.114.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms

Mike
Nov. 28, 2010, 7:17 p.m.
Pinging nfscars.net [208.100.57.180] with 32 bytes of data:
Reply from 208.100.57.180: bytes=32 time=1668ms TTL=109
Reply from 208.100.57.180: bytes=32 time=1821ms TTL=109
Reply from 208.100.57.180: bytes=32 time=1955ms TTL=109
Reply from 208.100.57.180: bytes=32 time=1162ms TTL=109

Ping statistics for 208.100.57.180:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1162ms, Maximum = 1955ms, Average = 1651ms

Search Forums

Active Topics

Notifications

You currently have no notifications.

{[{ notification.title }]}

{[{ notification.created|timeAgo:'MM/dd/yyyy' }]}
{[{ notification.sender.display_name }]}
older notifications mark all as read
Shoutbox
{[{ shout.created|timeAgo:'MM/dd/yyyy' }]}