I have been a loyal and committed user of DotnetNuke and have recommended this CMS to many friends here in Bangkok.  There has been a loyal following here - but the general consensous is that maybe it is time to do something else.  I am using DNN as the CMS for a CRM application at the largest private hospital group in BKK which consists of 24 hospitals.  I just cannot wait any longer - something needs to be addressed!

I truly respect the dedicated effort of the "core" team and their relentless commitment but there are serious problems in the latest 3.x release that need immediate attention -

On the Server(s) - there are 24 (one for each hospital)  I have installed Windows 2003 Enterprise, SQL 2000, Reporting Services and DNN  -  THAT IS IT!  All the latest patches, service releases, etc. and the machine is meticously maintained.

Updating a Page - literally takes on a dedicated server with 4g of memory and 247 gig of storage literally 10 - no this is not an error - 10 minutes - IF I AM LUCKY - to update the page if you are fortunate enough NOT to receive a "TimeOut" error message.

Delete a Page - this works ok if based on the following example:

PAGE Heirarchy
   Page 1
   Page 2
   Page 3

No problems deleting page 1,2, or 3 - BUT to delete the Page Heirarchy - it does not work .........    I have tried over 20 times and I either get a "TimeOut" message or "Not Authorized" error message....   The PAGE HEIRARCHY cannot be deleted and of I go into the database to remove the entry or flag "IsDeleted" it still burps!

Moving a Page - same behavior as Updating a Page - literally takes forever to move up in the heirarchy if I am lucky enough to not get a "TimeOut" or "Not Authorized" Error message.

Initial Load Time - Http://localhost/dnn virtual  virtual directory / default.aspx (or whatever someone else calls it) - but on average ot takes 5 minutes to load.  Yes, I have used HTTP Compression and NO difference.

Deletion of Links - I upgraded from DNN 2.X (some issues - but very easy to fix) and I still have deleted links in the database and in 3.X if I delete and remove from recycle bin they still exist within the database - Why?

File Upload - You can verify (nice feature) that you have a valid .dnn file to upload but signed on as Admin - file never gets uploaded!  You sign on as HOST and use File Manager to upload file - does not work!  But if you upload Custom Module - WORKS - why? 

Lets not even mention the SCHEDULER! From my humble perspective - you should just "turn off" or disable!

I can go on for another hour - but it will not do myself or anyone else any good! 

So I need an answers -  LIKE NOW!

Are these issues going to be fixed in the upcoming release?

When is the next release date - and is it realistic?

 I truly apoligize if I have offended ANYONE - that is not my intention - but this is becomming beyond critical!

Thank you and best regards,

Joe Harris

If you are on 3.x and upgraded from 2.x, there is another thread where some of your issues are confirmed.   This might be related:  http://forums.asp.net/860989/ShowPost.aspx

I will say on localhost (even on a fast, new computer with 1gb of ram) performing some tasks take forever or simply hang.  This includes changing settings, deleting a page, clearing cache, etc.     I have no issue however with the same code and same database on a shared server.

Maybe localhost has issues to do firewall, broadband router, etc....   I do not know but wish I did.

on most dnn sites i have installed, tested or uesd, the pages load about as fast as you can expect any web app to load.  i am pretty positive your issue is a local server config issue, and not dnn specific.  i would actually suggest installing some other asp.net applications in the same manner, and see if the result is similar. 

Brian_C - Thank You for your Reply!

The CRM application using DNN is behind the firewalls(s) - no one is allowed to access the CRM from any remote facility ( internet, dail_up, etc.) and we have ensured that all ports and protocols are closed fronm an external access.

The DNN CMS "flew" - I mean performed very well prior to upgrading from 2.X to 3.X. 

We have other ASP.Net ( 3 to be exact) applications used within the Laboratory and they just :scream"! Really, they just perform excellent while receiving data from some Lab machines - also, there is an out patient ASP applications that manages out patient wait time to see the doctor and then the diagnosis time the Doctor spent with the patients with Tablet PC 's that use an ASP.Net application and the same result - they just "scream" - really perform! 

So I have installed some performance evaluation tools a friend of mine from IBM gave me from the Performance Evaluation Center in Roanoak, TX - and everything points to DNN - to refine a bit further - what hits the CPU is taking in conjunction with page access - so I just am at a cross-roads about DNN.

Thank You

Joe Harris

 

 

Thank You for your Reply!

The CRM application using DNN is behind the firewalls(s) - no one is allowed to access the CRM from any remote facility ( internet, dail_up, etc.) and we have ensured that all ports and protocols are closed fronm an external access.

The DNN CMS "flew" - I mean performed very well prior to upgrading from 2.X to 3.X. 

We have other ASP.Net ( 3 to be exact) applications used within the Laboratory and they just :scream"! Really, they just perform excellent while receiving data from some Lab machines - also, there is an out patient ASP applications that manages out patient wait time to see the doctor and then the diagnosis time the Doctor spent with the patients with Tablet PC 's that use an ASP.Net application and the same result - they just "scream" - really perform! 

We had those 3 ASP apps installed on the server with DNN and then removed and installed on another server within the LAB - but nothing else changed within the Server with DNN installed. 

So I have installed some performance evaluation tools a friend of mine from IBM gave me from the Performance Evaluation Center in Roanoak, TX - and everything points to DNN - to refine a bit further - what hits the CPU is taking in conjunction with page access - so I just am at a cross-roads about DNN.

Thank You

Joe Harris

 

josun wrote:

I have been a loyal and committed user of DotnetNuke and have recommended this CMS to many friends here in Bangkok.  There has been a loyal following here - but the general consensous is that maybe it is time to do something else.  I am using DNN as the CMS for a CRM application at the largest private hospital group in BKK which consists of 24 hospitals.  I just cannot wait any longer - something needs to be addressed!

Take a look at this announcement. Maybe it is something for you?

Cheers,

DocHoliday

Hey josum - can you take a look at TabPermissions table ? Are there too many records for every tab ?

Can you install a fresh new copy (not an upgrade) of DNN in a different directory and look at the performance?

I would 2nd Micheal's suggestion.

Install another clean 3.0.12 DNN (not an upgrade) in the same environment and do some performance testing.

It's the only way to be sure.

The first thing I would do is try and figure out if it's something on the ASP.NET end or something on the SQL end.  In other words, is a query taking an exceptionally long time to load, or is ASP.NET hanging during some processing.  I'd use SQL Profiler to check it out, set a duration filter of 1000 ms and run a trace.  That'll filter out most of the garbage and catch any query that is taking longer than 1 second to execute.  If it is a query that is hanging, grab the sproc out the profiler and run it in Query Analyzer, check out the tables, look at the execution plan, find out what the heck is taking so long.

If it's not a query, hook up a development copy of DNN to your SQL DB and see if you have the same performace issues.  Hopefully you can reporduce it, trace it through the code and find out exactly where it's blowing up.

Yeah that'll take a bit of work and time, but I'm sure the day or two debugging will be a heck of a lot better than trying to replace DNN now.

Wish I could be more helpful, but it's kinda hard to poke around from 10,000 miles awaly :-(

did not the link I posted confirm other people saying after an upgrade certain functions hang or are slow?  Maybe not ....

Joe, If it's possible for you to make a backup of your db and zip it up, I'll be glad to to take a look at it.

I am also running into issues with performance.  We have narrowed down our performance to IIS 6 we have the same exact version of DNN3 hitting the same database and the performance of IIS6 is 5x as slow as the IIS5 version.  Does anybody have any hints about what settings I should check that might improve the performance?

Tim

Everyone - SINCERE THANKS!

Okay  the first thing:

We have already evaluated every SQL statement we are using within MS Reporting Services and there is NOT 1 that does not ececute in less than 4 seconds - and 4 seconds is the longest our of over 400 Stored Procedures.  Most are lightning!  We have reviewed all execution plans, etc. 

This includes MDX going against Analysis Services to display within MS Reporting Services data from Cubes within AS as well as pre-defined AS Reports.  We are using MS Reporting Services in a pretty advanced way (?) to provide the capability of a THin WEB OLAP via MS Reporting Services without OWC and the other junk you need on a deskop.  This is purely a server side application.

Within DNN we only call via a URL a MS REporting Services report based upon a menu function within DNN. 

But - I call http://localhost/dnn virtual director /default.aspx or I call http://Server name/dnn virtual directory/default.aspx and everything comes to a grindng halt. 

J7Mitch - I can send the DNN data base - but I could never send the hospital data base! 

In my heart of hearts - there is something left over in the upgrade from 2.X to 3.X that is lingering somewhere - I am sure that is the problem. 

Any help is sincerely appreciated.

Best Regards,

Joe Harris

josun wrote:

In my heart of hearts - there is something left over in the upgrade from 2.X to 3.X that is lingering somewhere - I am sure that is the problem.

I agree. As I wrote before, a clean installation of the same DNN version on the same machine (please note: same machine) is behaving normal and performs very fast (IIS6). Therefore, something must have silently screwed up the 2.x install during the upgrade process.

Cheers,

DocHoliday