Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryPerformance issue with 600 entriesPerformance issue with 600 entries
Previous
 
Next
New Post
10/11/2011 1:18 PM
 
Hi Steve,

I'm using DNN: 06.00.02 (72) with Repository 3.5.4

So would be prepared to test your 6.x patch.  Can you also explain the funny thing with the dropdown category/sort order filtering when in View mode ? Or is this a combined problem at all ?

Regards

Thomas
 
New Post
10/11/2011 1:35 PM
 
Thomas,
Thanks for the offer. I will have something for you in a little while.

BTW:  If you're running DNN 6.X you should be using Repository 3.5.5.  It's a beta release, but the changes that were necessary to be compatible with DNN 6.x were small and extremely low risk. I would suggest first, upgrade to the existing 3.5.5. It won't solve your issues, but it's the version you should be running if you are running DNN 6.x

I will have a new 3.5.5 release later today that (hopefully) will address the performance

Current 3.5.5 beta
http://gooddogs.com/Downloads.aspx
 
New Post
10/11/2011 3:21 PM
 
Here's the test file for the following configuration:

DotNetNuke : 6.X
Repository Module:  3.5.5 Beta



*NOTE*  THIS IS ONLY IF YOU ARE RUNNING REPOSITORY MODULE VER 3.5.5 (Beta).


1) backup the DotNetNuke.Modules.Repository.dll file in your bin folder
2) down a new .dll from here http://www.gooddogs.com/files/dnn6/do...
3) place it in your bin folder
4) recycle your application

now, try your site and see if the performance is now acceptable

Reminder: This is only if you are running DotNetNuke 6.X and Repository Module version 3.5.5 Beta

thanks
 
New Post
10/12/2011 5:13 AM
 
YES,

performance is really good now. I have put the dashboard at the left side and the page renders in about 3 sec. When left and navigated back it comes even faster.

What's left now is that I can not change the filter or use the dashboard as filter when I am in View mode
Also I can not change the modules header text, but I think this is an issue of the Editor provider.
This also does not work on changing text in HTML modules etc.
If someone knows how to fix that - let me know...
 
New Post
10/12/2011 6:43 AM
 
Addendum to the errors I receive sometimes:
This happens when you change from View to Edit or vice versa.

AssemblyVersion: 6.0.2

PortalID: 0

PortalName: Acentic support web

UserID: 1

UserName: host

ActiveTabID: 137

ActiveTabName: Document Repository

RawURL: /support/Support/DocumentRepository/tabid/137/Default.aspx

AbsoluteURL: /support/Default.aspx

AbsoluteURLReferrer: http://support.acentic.net/support/Support/DocumentRepository/tabid/137/Default.aspx

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: b4ffea81-9477-4fd5-a85f-23e3b30eccee

InnerException: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: System.Web.UI.Control.LoadViewStateRecursive

StackTrace:

Message: DotNetNuke.Services.Exceptions.PageLoadException: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request. ---> System.Web.HttpException: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request. at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Control.LoadChildViewStateByIndex(ArrayList childState) at System.Web.UI.Control.LoadViewStateRecursive(Object savedState) at System.Web.UI.Page.LoadAllState() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Source:

Server Name: IP-0AE45D7D

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryPerformance issue with 600 entriesPerformance issue with 600 entries


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out