Well, I'm sorry to post about performance of the module as this has already been discussed a while before, but I'm having big trouble:

I just upgraded my DNN installation from 5.x to 6.0.1 to overcome performance issues, but I's not getting better.
Environment:
Amazon hosted virtual server with IIS 7 and SQLExpress (limited to 768 MB Ram)
Repository contains about 600 entries in about 20 categories. Relation grmRepositoryCategoryObjects contains 800 entries
Display of the module takes about 20-30 seconds sometimes Browser times out, sometimes and Error comes back.
I  identified one single query to take most of the time which is the grmGetRepositoryCategoryObjects and called more than 10000 times.
I can not quite understand why this happens, but this is not desireable result for such a request.
In the query execution plan I can see TableScan but would expect IndexScan instead, but I'm not the SQL Guru.

If you could help me to find the cause I would be grateful.

Hi there,

additional information:

We had a dashboard beside the repository module to select category. I thought this could be the cause of the problem and removed it..... but no difference.

Additionally we are facing the fact that selecting a category from the repositories own dropdown list will not filter the selected category, but remain in the "all items" list mode.

Any progress or at least confirmation on the problem ?

Best regards

Thomas

I'm not sure the problem is with the indices when the stored procedure is firing once for every record found in the first result set.

For instance let’s say there are 1000 records.  The first procedure takes 2 seconds to run.  Then the next procedure – assuming it is fully optimized – takes several milliseconds to run.  Let’s say 50ms.  50ms * 1000 = 50000ms = 50 seconds – way too long to wait for the page to load…

We're looking into the source code further to see if we can offer any solutions.