URGENT Really Slow After Editing and Errors - in production

We just moved our 4.2 site into production.  It has been handling our traffic okay with the exception of making edits.

When we try to make edits to the site, it will run really slow for anywhere from 5-60 minutes.  Some pages are taking 10 minutes to load.  Our CPU utilization spikes to over 90 percent and the connection count drops severly.

I have looked in the Sitefinity Error logs and see this.  Any ideas??

----------------------------------------
Timestamp: 9/23/2011 6:11:55 PM

Message: HandlingInstanceID: b2aa25b3-fd28-4bc9-9155-f54cf33575be
An exception of type 'Telerik.OpenAccess.Exceptions.DataStoreException' occurred and was caught.
------------------------------------------------------------------------------------------------
09/23/2011 13:11:55
Type : Telerik.OpenAccess.Exceptions.DataStoreException, Telerik.OpenAccess, Version=2011.2.713.3, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342
Message : System.InvalidOperationException: Invalid attempt to call Read when reader is closed.
   at Telerik.OpenAccess.RT.Adonet2Generic.Impl.ResultSetImp.next()
   at OpenAccessRuntime.Relational.fetch.FetchResultImp.rsNext()
   at OpenAccessRuntime.Relational.fetch.FetchResultImp.hasNext()
Source : Telerik.OpenAccess.Runtime
Help link :
InnerExceptions : System.Exception[]
FailedObject :
BackendError :
Reason : Runtime
CanRetry : False
Data : System.Collections.ListDictionaryInternal
TargetSite : System.Exception Throw()
Stack Trace :    at Telerik.OpenAccess.RT.ExceptionWrapper.Throw()
   at OpenAccessRuntime.DataObjects.PCStateMan.handleException(Exception x)
   at OpenAccessRuntime.DataObjects.PCStateMan.getObjectFieldImp(PersistenceCapable pc, FieldMetaData fmd, Object currentValue)
   at OpenAccessRuntime.DataObjects.PCStateMan.getObjectField(PersistenceCapable pc, Int32 field, Object currentValue)
   at Telerik.Sitefinity.Pages.Model.PageData.OpenAccessEnhancedGettemplate(PageData )
   at Telerik.Sitefinity.Pages.Model.PageData.get_Template()
   at Telerik.Sitefinity.Modules.Pages.PageHelper.GetTheme(PageData pageData)
   at Telerik.Sitefinity.Modules.Pages.StaticPageData.SetPageDirectivesInternal(PageData pageData)
   at Telerik.Sitefinity.Modules.Pages.StaticPageData..ctor(PageData pageData, PageDataProvider provider)
   at Telerik.Sitefinity.Web.ResourceCombining.InMemoryPageRender.GetPage(PageNode pageNode, PageDataProvider provider, HtmlTextWriter writer, HttpContext& context)
   at Telerik.Sitefinity.Web.ResourceCombining.InMemoryPageRender.RenderPage(PageNode pageNode)
   at Telerik.Sitefinity.Publishing.Pipes.PageInboundPipe.RenderPage(PageNode node)
   at Telerik.Sitefinity.Publishing.Pipes.PageInboundPipe.SetWrapperObjectProperties(WrapperObject wrapperObject, PageNode node)

Additional Info:

MachineName : DMZDISTWEB
TimeStamp : 9/23/2011 6:11:55 PM
FullName : Telerik.Sitefinity.Utilities, Version=4.2.1650.0, Culture=neutral, PublicKeyToken=b28c218413bdf563
AppDomainName : /LM/W3SVC/2/ROOT-3-129612649448712581
ThreadIdentity :
WindowsIdentity : NT AUTHORITY\NETWORK SERVICE
Requested URL : http://www.fortbendisd.com/
    Inner Exception
    ---------------
    Type : System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Message : Invalid attempt to call Read when reader is closed.
    Source : Telerik.OpenAccess.Runtime
    Help link :
    Data : System.Collections.ListDictionaryInternal
    TargetSite : Boolean next()
    Stack Trace :    at Telerik.OpenAccess.RT.Adonet2Generic.Impl.ResultSetImp.next()
       at OpenAccessRuntime.Relational.fetch.FetchResultImp.rsNext()
       at OpenAccessRuntime.Relational.fetch.FetchResultImp.hasNext()



Category: ErrorLog

Priority: 0

EventId: 9010

Severity: Warning

Title:Enterprise Library Exception Handling

Machine: DMZDISTWEB

App Domain: /LM/W3SVC/2/ROOT-3-129612649448712581

ProcessId: 3464

Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe

Thread Name:

Win32 ThreadId:6032

Extended Properties:
----------------------------------------

Everything operated normally on the front end until approximatly 1:15 p.m. when I started makeing edits.  The first time the episode did not last long, maybe 5 minutes.  The second time it lasted over 22 minutes.

This happened yesterday when we launched the site on three occasions.

Hi Anthony,
This problem begins to sound like you have your IIS application pool set to restart when certain system limits are met. When this happens sitefinity has to bootstrap again before it can respond which is generally a slow process. It can be the case that such restarts happen in an endless row for a very long period.
One way to diagnose if this is happening is to check your System events logs for entries with source WAS -with description like "The worker processes serving application pool '....' are being recycled due to ..."

You can also check what are your application pool settings:
If you have enabled CPU limit action ->KillW3wp
or
Recycling enabled with Memory Limit etc.

Please if you have such settings turned on try to change them not to recycle when this limits are met and see if the problem disappears.

Greetings,
Nikolay Datchev
the Telerik team

Nokolay,

Please see ticket #467564.  I have included screenshots of our AppPool there.  What you are describing looks like what we may be experiencing, but we are not seeing the errors you describe.

Hi Anthony,
Since we are dealing with your problem in your support ticket 467564 , i suggest we currently close the discussion here.
Greetings,
Nikolay Datchev
the Telerik team

Hi,
We have the same problem (ticket #456033), please let us know if you have find a solution.
Thanks

@mkavici
I had some strang spikes in 4.2 where the RAM usage would go up to 1GB and more.
As usually if possible state what version you are using 1650 or so and if possible update to the latest version of SF.

I know thats not allways possible but usually a good starting point.

Markus

Hello Markus Berchtold,
I also confirm that 4.2 had memory spike issues and it is better to upgrade to the latest official version. Also Mahmut problem in ticket 456033 will be addressed in 4.4. I guess we can close the ticket for now.

All the best,
Nikolay Datchev
the Telerik team