Welcome to WebmasterWorld Guest from 34.229.194.198

Forum Moderators: ocean10000

Message Too Old, No Replies

ASP.net potential performance problem

Main page takes 10 seconds to display

     
5:01 pm on Jan 30, 2009 (gmt 0)

Junior Member

10+ Year Member

joined:June 21, 2005
posts: 60
votes: 0


I'm pretty new to ASP.net, and was recently tasked with creating a project/task list. Essentially, it is a collection of everyone's tasks, what projects they are working on, and any comments.

The main page is a single .net page using the AJAX accordion control. It is a display page only...all editing is taken care of on separate pages. I give basic project information in the header as well as control buttons, and when the pane is opened, a gridview shows the associated tasks. The database is an access database.

With ~40 projects and ~180 tasks the pages takes 10ish seconds to load. That really worried me, especially with regard to future scalability. I tried checking the performance counters on the "server" (Windows XP, IIS 5) but they didn't seem to reveal the bottlenecks. Next, I tried two performance profilers, AQTime and ANTS with limited results. AQTime told me that my root directory had the problem (which I knew), but it wouldn't tell me where. I did notice in its event viewer that quite a few threads were created and destroyed in rapid succession, but I'm not sure why. I didn't attempt to multithread the application, so any threads it creates aren't mine. ANTS told me that most of my problem was thread blocking, but couldn't tell me more.

My big questions are:
1. How can I improve the performance of my page/find what is slowing me down?
2. Am I using the correct control? I'm wondering if using the accordion is part of my problem, and if I shouldn't be taking a different approach.

Thanks,

Casey

8:20 pm on Jan 30, 2009 (gmt 0)

Administrator

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month

joined:Jan 14, 2004
posts:864
votes: 3


First thing I would recommend is moving away from access to supply the information. Microsoft Access is not designed to handle this type of access. It can but usually it is the bottle neck. Microsoft Access is designed to be a single user DB, it was not designed to scale vary well. The threading issue's you are most likely noticing are probably around DB calls.

You can use the build in Trace options in asp.net to see where the slow downs are happening.
MSDN - ASP.NET Tracing Overview [msdn.microsoft.com]

You might look into refining the sql queries to improve the performance there or cache the data more if it doesn't change often.

[edited by: Ocean10000 at 8:21 pm (utc) on Jan. 30, 2009]

9:15 pm on Feb 3, 2009 (gmt 0)

Junior Member

10+ Year Member

joined:June 21, 2005
posts: 60
votes: 0


I don't think I'll be able to move off of access for a while, but I'll keep it in mind as we go forward.

I'll try out the trace and see what it says, as well as refine the queries and cache anything I can.

Thanks,

Casey

10:44 am on Feb 10, 2009 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member

joined:Feb 24, 2005
posts:965
votes: 0


Let me guess, you're a Windows Application developer that's just decided that web is easy? :p
 

Join The Conversation

Moderators and Top Contributors

Hot Threads This Week

Featured Threads

Free SEO Tools

Hire Expert Members