Hi,
We enabled memory caching although having AJAX components. Seems to improve the speed with 1s and a 'hanging' site is less likely. It is however still quite quite slow since images are downloaded after 1.5 s in total.
B.

We changed the execution time out setting in our web.config and then most (if not all) of our performance issues went away. This tells me that its a certain page or module or something on our site that is causing a long delay and then therefore causing the problem... not sure which page yet though or which module but I don't think we had this in 5.5. We will see though as more users post more details. Thanks, Chad www.datasprings.com

Hi,
It seems that if you authenticate as admin/ host the performance drops. I assume this is related to the caching not being enable for a single user. Or it is possible to cache for a while? I also find an authenticated user having the strange error without any stacktrace. I will check the portal/ server logs which pages he/ she visited lately.

I also encountered these errors today:

AssemblyVersion: 5.5.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: / __doPostBack(&
AbsoluteURL: / __doPostBack(&
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: aa5c3a0b-2d86-4d3b-83d8-ee1757be233d
InnerException: A potentially dangerous Request.Path value was detected from the client (:).
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.HttpRequest.ValidateInputIfRequiredByConfig
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: A potentially dangerous Request.Path value was detected from the client (:). ---> System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (:).at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)--- End of inner exception stack trace ---
Source:
Server Naam: xxx

AssemblyVersion: 5.5.1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: / WebForm_DoPostBackWithOptions(new/WebForm_PostBackOptions("dnn$dbbSearch$lnkSearch",/"",/true,/"Search",/"",/false,/true))
AbsoluteURL: / WebForm_DoPostBackWithOptions(new/WebForm_PostBackOptions("dnn$dbbSearch$lnkSearch",/"",/true,/"Search",/"",/false,/true))
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: d09b80ff-ddf5-4221-87b9-42cb53d43fb0
InnerException: A potentially dangerous Request.Path value was detected from the client (:).
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.HttpRequest.ValidateInputIfRequiredByConfig
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: A potentially dangerous Request.Path value was detected from the client (:). ---> System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client (:).at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)--- End of inner exception stack trace ---
Source:
Server Naam: xxx