Slow Response / Performance On Stormtrack

[Skip Talbot]

One of the mods should shoot Tim an email

Email was sent on Friday

 

[jeremy wilson]

Slower than honey going up hill in the wintertime.

 

[Mark Blue]

Email was sent on Friday

That's about all a guy can do I guess...

 

[Robert Dewey]

Blazingly fast this morning!

robert@robert-Ubuntu-Notebook:~$ ping -c 10 -s 256 google.com
PING google.com (74.125.225.18) 256(284) bytes of data.
264 bytes from 74.125.225.18: icmp_req=1 ttl=54 time=26.0 ms
264 bytes from 74.125.225.18: icmp_req=2 ttl=54 time=28.4 ms
264 bytes from 74.125.225.18: icmp_req=3 ttl=54 time=33.8 ms
264 bytes from 74.125.225.18: icmp_req=4 ttl=54 time=30.1 ms
264 bytes from 74.125.225.18: icmp_req=5 ttl=54 time=32.1 ms
264 bytes from 74.125.225.18: icmp_req=6 ttl=54 time=23.0 ms
264 bytes from 74.125.225.18: icmp_req=7 ttl=54 time=29.9 ms
264 bytes from 74.125.225.18: icmp_req=8 ttl=54 time=23.4 ms
264 bytes from 74.125.225.18: icmp_req=9 ttl=54 time=30.3 ms
264 bytes from 74.125.225.18: icmp_req=10 ttl=54 time=30.3 ms

--- google.com ping statistics ---
10 packets transmitted, 10 received, [b]0% packet loss[/b], time 45338ms
rtt min/avg/max/mdev = [b]23.074/28.783/33.882/3.379 ms[/b]
robert@robert-Ubuntu-Notebook:~$ ping -c 10 -s 256 stormtrack.org

PING stormtrack.org (64.150.187.170) 256(284) bytes of data.
264 bytes from 64-150-187-170.dedicated.abac.net (64.150.187.170): icmp_req=1 ttl=48 time=118 ms
264 bytes from 64-150-187-170.dedicated.abac.net (64.150.187.170): icmp_req=2 ttl=48 time=115 ms
264 bytes from 64-150-187-170.dedicated.abac.net (64.150.187.170): icmp_req=3 ttl=48 time=600 ms
264 bytes from 64-150-187-170.dedicated.abac.net (64.150.187.170): icmp_req=4 ttl=48 time=828 ms
264 bytes from 64-150-187-170.dedicated.abac.net (64.150.187.170): icmp_req=6 ttl=48 time=1700 ms
264 bytes from 64-150-187-170.dedicated.abac.net (64.150.187.170): icmp_req=8 ttl=48 time=1500 ms
264 bytes from 64-150-187-170.dedicated.abac.net (64.150.187.170): icmp_req=10 ttl=48 time=118 ms

--- stormtrack.org ping statistics ---
10 packets transmitted, 7 received, [b]30% packet loss[/b], time 9027ms
rtt min/avg/max/mdev = [b]115.222/711.641/1700.823/619.456 ms[/b], pipe 2
robert@robert-Ubuntu-Notebook:~$

 

[Robert Edmonds]

Really slow, really disappointed...

 

[John Farley]

Well, after a half hour or so I finally made it here. I know this site is run on a volunteer basis, but this has been going on for several days and it has rendered the site useless at a high-interest time. Somebody really needs to do something.

 

[Jayson Prentice]

It is terribly slow at the moment... As mentioned above it has been going on for a while now with no response that I see of...

Anyone care about the site and its' posters anymore??

At least mention that the problem is known and someone is going/trying to fix it...

 

[Ryan McGinnis]

Maybe we should all spring for a bat signal.

 

[GPhillips]

Everything is responding fast now. Something was done.

 

[Jason Foster]

Seems good now for me. I posted on FB about it basically being hosed earlier, I think last night or this morning (memory is fuzzy still....24 hours of driving will do that).

Also noticed TimV either block me or deleted his FB profile. Jee...I wonder. That's fair as harsh as I've been.

 

[Scott Weberpal]

Fairly sure he outright deleted facebook.

 

[John Farley]

Appears to be working fine now; thanks much!

 

[Jesse Risley]

I emailed Tim V. Friday evening about this, and it appears that is has been fixed as of early this afternoon. Skip Talbot also posted previously that Tim had been notified.

These types of site-related (server?) issues are not something that the moderators can fix given our limited administrative privileges. Also, I doubt that Tim has blocked anyone on Facebook, as I can't access his page either.

 

[Ryan McGinnis]

Woohoo! Thanks for the fix! Working great now.

 

[Tim Vasquez]

The problem has been a DDOS attack... I worked on this yesterday and this morning and it appears we're now running much, much better. I am sorry that I have not updated you all properly about it. I figured it was fixed, then had found 5 minutes later it was broken again. We've been running about 2 hours with no problems now, knock on wood.

That's correct about my FB profile, but it's just a prioritization issue. It is on temporary vacation until I'm certain I can tend to it properly.

Tim