Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>EDIT: From reading your question again, you might be using the asp.net web site solution type. This is not pre compiled when you are debugging and the first time you request a page it compiles it into a class in your asp.net directory. The dll for the class is then loaded into the app domain with a funny name like the one you mentioned. This happens the first time you request one of these pages and when you want to deploy you can pre compile your site to increase performance.</p> <p>If you are seeing "loading xyz.dll" it means the app domain is loading in stuff to be used by the application. This happens when you need to run code from required dlls (in your case probably third party libs) that have not yet been loaded into the app domain. This is good because it means a page that uses a library but has never been called, never loads that assembly into memory. You could move this hit from first page request to application load by pre loading all the assemblies in your bin into the app domain on application start. It is a trade off between use of memory against speed of requests. This question is a good place to start with that:</p> <p><a href="https://stackoverflow.com/questions/3021613/how-to-pre-load-all-deployed-assemblies-for-an-appdomain">How to pre-load all deployed assemblies for an AppDomain</a></p> <p>You can get a good overview of your page lifecycle times by using the trace functionality in asp.net. This can be set in the web.config file as described in this article:</p> <p><a href="http://msdn.microsoft.com/en-us/library/94c55d08.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/94c55d08.aspx</a></p> <p>Viewing the trace.axd page will tell you times off the various server events and make it really easy to see where you are slow.</p> <p>If the page still takes a long time to render, there are client side considerations such as</p> <ul> <li>is your page very large</li> <li>are you interpreting javascript before all the html and css was written</li> <li>is your network slow </li> <li>are you sending many css and js files? most browsers limit the number of concurrent resource downloads. maybe consider rolling a few css files into one, on your production environment at least</li> <li>are you employing client cache. you can tell the browser to cache something for a period of time. there are ways to invalidate this cache if your content requires to be updated.</li> </ul> <p>This can be debugged using client side tools such as firebug or the developer tools in chrome.</p>
    singulars
    1. This table or related slice is empty.
    1. POASP.NET page load time question
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPeter Short
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POASP.NET page load time question
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COplease let me know if this helped, if its not the answer it would be good to know why :)
      singulars
      1. PO
      1. USPeter Short
    2. COIndeed, the website uses a lot of dll's. Around 50 and plenty of JavaScripts and CSS files. I will investigate if any of the javascript cause any bottlenecks. Fortunately, this doesn't happen too often, most of the time the speed is good. Like, one big duration for a customer and then everything goes back to normal, like a spike. So I'm considering, either this happens after a IIS reset, recycle or something similar or temporary network problems. Does the start/end request also count the time needed to send the page to the client's browsers?
      singulars
      1. PO
      1. USNial
    3. COYes, the start and end request events are done on the server so the client will still be waiting but these events are really quite fast. What you are describing sound like just in time compilation so maybe you should look at pre compiling your website. If its not a dll loading thing then tracing will help you narrow your search to see where the slow code is.
      singulars
      1. PO
      1. USPeter Short
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload