Jack of all trades, master of none.
Good news and Bad news
Published on May 22, 2006 By T-Man In WinCustomize News

Well, it appears that our database servers performed much better while the personal pages were off.  Not only was the database happier but we saw a significant increase in traffic to WinCustomize because there were less problems.  So its good that we have seen our traffic increase.   But its bad because it means there is a problem with the personal pages that is causing significant database congestion.

So here is the plan.  Later today (around 3:00) we plan on turning the personal pages back on for a short time (about an hour).  During this time we are going to be profiling database activity so we can try to find the problematic areas.  Then we will turn the Personal Pages back off until we can get the problem(s) corrected.  But since we do not know the exact cause of the problem we do not know for sure how long they will be down.  We will keep you informed.


Comments (Page 1)
on May 22, 2006
Lets hope for the best! 3 in what time zone?
on May 22, 2006
3 EST
on May 22, 2006
Hmmm... No WONDER I couldn't get to my stuff!
on May 22, 2006
What time is that in real money?
on May 22, 2006
....about six inches...
on May 22, 2006

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding

That's what I got trying to read this thread

on May 22, 2006
So what's the good news? Leeds Utd didn't get promotion, hehehe
on May 22, 2006

Glad I did not post my tutorial images on my personal pages!

Taking a break for a good bit anyway, so will check back later this summer...

Have a good summer all!

on May 22, 2006
If using Active Directory then there needs to be a cleanup of "Garbage" data. Usually this is done by default every 12 hours of objects that are tombstoned, then defragged. You can set the tombstone process interval by editing the ADSI. This may be something that will help you out?
on May 22, 2006
Hmm...let's see if I've got this right:
site o.k. but needs to be better


so must open it up and fix it


before...



So we've just gotta hang
'til techs are done and
it's better than ever...?
on May 23, 2006
This may be displaying my ignorance in these matters, but why not put the personal pages on a different server?
on May 23, 2006

This may be displaying my ignorance in these matters, but why not put the personal pages on a different server?


This wouldn't solve our problem because each website is tied directly to the same main database. The database is the key point where all websites rely upon it to function well. When the database is unhappy, the websites are unhappy. If a website, such as the personal pages, causes the database to perform poorly, then this causes a cascading effect for all of the websites. As mentioned by Brad (frogboy), a new super database server is on the way, and this will help a little, but ultimately, fixing the cause of the problem is the best solution. This is why the personal pages must be addressed, as there is only so much hardware you can upgrade until the problem pops up again.

on May 23, 2006

We have identified some problematic areas in our code and we are working on them to refine them.  I suspect that we will do another test later today to test the changes we make.

 

This may be displaying my ignorance in these matters, but why not put the personal pages on a different server?

THe problem is not with the server that the website is on, the problem is with the way the website interacts with the central database.

on May 23, 2006
In just a couple minutes we will be turning the personal pages on again for a about an hour while we do some more tests.
on May 23, 2006
Sure seemed much more responsive and without slowing down other section loads. Of course, I have no idea what traffic load you have at this time of day.
Meta
Views
» 2827
Comments
» 32
Sponsored Links