August 5, 2009 at 11:14 pm
I'm not sure what goes on with the SSC servers from 23:00 to after (at least, maybe longer) 01:00 EDST (Zulu-5), but the response times are terrible especially when posting a response. Most of the time I have to wait ten minutes either for a timeout or to press the back button. Then, I manually tell the system to subscribe to the post.
I suspect, due to all the quadruple posts at night (where I'm at), that a lot of folks are having a similar problem and are doing the same thing but then hitting the SUBMIT button again... and again... and again.
I know I should take the hint and simply go to bed but can you folks make this less painful for the rest of the world?
Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 12, 2009 at 3:23 am
Hi Jeff,
I'm not sure exactly what Jobs start at around that time, but we'll be looking into it. We are looking into adjusting the way that we do the newsletter to dramatically reduce the load on the servers, which should help with these sort of problems.
Mel
Mel HarbourProject ManagerRed Gate Software
September 11, 2009 at 1:28 am
between 7am and 9am GMT, replying to topics is almost unworkable, waiting for about 2 minutes for it to time out.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
September 11, 2009 at 10:15 am
We start sending the newsletter at 9pm MST most days. That's usually what the slowdown is. At times I run an hour late, but it seems the first hour or two it's really slow.
New hardware is being spec'd out now and we're trying to decide what makes sense in terms of horsepower and $$. This is a business, and it's expensive to run this site.
We have talked about backing the time down to an earlier hour, but that impacts those people working late in the US. I used to start sending at 8pm MST, which is 3am GMT.
September 11, 2009 at 1:57 pm
I guess I'd have to ask, "What changed?" This didn't use to happen ever.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2009 at 2:18 pm
Do you mean why is it slow those times?
I can't quite be sure. I'm not the infrastructure guy, nor the developer, nor DBA. I gave up control to focus on content, and so I'm not in the loop.
As far as I know, nothing much other than load. My guess is that we've been collecting data, storing things off, tables growing, and we hit a point where the optimizer fundamentally examined the code differently.
We're working on making some changes, but in the scheme of things, this isn't a critical priority.
September 11, 2009 at 4:41 pm
Actually, I apologize... I had my trobleshooting hat on. It's actually none of my business and you folks have been making constant improvements to the site and the user experience. And, as you imply, reaching a "tipping point" is likely exactly what happened.
Thanks, Steve.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2009 at 7:34 pm
No worries. We're working to slowly improve things over time. New hardware is being spec'ed and argued about now, and I think that will help.
I suffer the same issue here. After about 10, I give up on getting work done on the site until the next morning.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply