06-07-2013, 08:24 AM #1
Sorry about the outage last night, folks
Twins Daily was literally flooded with server requests as the Twins prepared for their 6:30pm first round pick last night. We apologize for the server going down (it appears that it went down for only some of us) but appreciate that so many of you view us as THE Twins news resource, particularly when it comes to minor league and draft news.
I'm in talks with the hosting company to see what we can do to prevent this from happening again when the trade deadline approaches. Given that we shouldn't see a bum's rush of traffic at EXACTLY the same moment today due to the drawn-out nature of the later draft picks, the server should support the traffic just fine, even if the overall number of queries is the same as it was yesterday.
If anything, thanks for flooding the server. In a weird sort of way, it's a good thing as it means you all really like us.
06-07-2013, 08:29 AM #2
- Liked 10 Times in 8 Posts
- Blog Entries
For what it's worth, MLB.com had problems last night too.
06-07-2013, 08:31 AM #3
- Liked 72 Times in 43 Posts
06-07-2013, 08:35 AM #4
Many Bothans died to bring us those draft results...
And is Bud Selig really incapable of saying two-thousand thirteen?
06-07-2013, 08:36 AM #5
It's not uncommon for this kind of thing to happen, especially early in a site's life. The only other time we saw traffic similar to yesterday was after the Span trade and we were on a different server at that point. Twins Daily has since changed quite a bit and is considerably more resource-intensive today than it was at that point (due to technical things that aren't worth discussing).
Anyway, we're going to work on the problem and figure out what we need to do to avoid it happening again.
06-07-2013, 08:36 AM #6
06-07-2013, 10:38 AM #7
Would this also be why the site has been extremely slow to load? It actually is worse this morning, both from home and work. (Using Firefox.)
06-07-2013, 11:01 AM #8
- Liked 38 Times in 25 Posts
- Blog Entries
06-07-2013, 11:18 AM #9
It's really hard to predict when and where the traffic wall will be hit and I didn't see this one coming AT ALL. I guess the changes I made to the system a few months back eat resources like crazy. Unfortunately, they were absolutely necessary to make.
06-07-2013, 11:36 AM #10
No worries ... I figured it was traffic issues. Growing pains. I'll be patient. More irked, actually, that MLB.TV was annoyingly difficult last night. I might just suck that up and buy the Extra Innings package for the 2nd half of the season.