Gc.com Painfully Slow & Throwing Errors

[+Thot]

I assume the administrators are aware, but I thought I'd mention it just in case

[+woof n lulu]

Yes they seem to be aware

[+Renegade Knight]

That is lasted into Monday was the suprise.

[Jeremy]

I'm resetting refresh on the machine every hour, which should hopefully clear it up.

[+Thot]

Well, it's Tuesday morning and it's been failing for the last couple of hours. I haven't been able to look something up for a friend, because I can't get to the page. I've tried about 5 times spread out over time.

[+Thot]

Server Error in '/' Application.

--------------------------------------------------------------------------------

 

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

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

 

Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

 

Source Error:

 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

 

Stack Trace:

 

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

  System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) +723

  System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +45

  System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) +5

  System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304

  System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77

  System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) +38

  Groundspeak.Web.SqlData.SqlConnectionManager.FillDataSet(String sql, Database database) +177

  Groundspeak.Web.SqlData.SqlUserController.GetCalendarDateData(Int64 UserID, DateTime DateFrom, DateTime DateTo, WptDataSources DataSource) +393

  Groundspeak.Web.User.GetCalendarDates(Int64 UserID, DateTime DateFrom, DateTime DateTo, WptDataSources DataSource) +111

  Geocaching.UI.my_default.BindCalendar() +337

  Geocaching.UI.my_default.DisplayUserDetails() +1760

  Geocaching.UI.my_default.Page_UserLoggedIn(Object sender, EventArgs e) +56

  Geocaching.UI.WebformBase.IsLoggedIn() +1089

  Geocaching.UI.my_default.Page_Load(Object sender, EventArgs e) +138

  System.Web.UI.Control.OnLoad(EventArgs e) +67

  System.Web.UI.Control.LoadRecursive() +35

  System.Web.UI.Page.ProcessRequestMain() +753

 

 

--------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

[+as77]

This is like the January effect on the stock market. When it was discovered, it started to shift backwards. After some time the January effect occured in early October. Then disappeared.

 

What we have here is this: people find that the website is overloaded during weekends. So everyone starts logging on Mondays. But then the server will be overloaded on Mondays, too, so people start logging on Tuesdays. In the end, the effect will disappear and the server will be overloaded all the time...

[Jeremy]

I just offloaded some of the larger queries to another database. Hopefully that should speed up the site in general terms.

[+beejay&esskay]

And suddenly the overworked hamsters get a second wind.

 

Things are moving fine now.