8 Replies

The Server Time is the sum of all individual network requests from the time the request is sent from the browser until the first byte came back. If you have a web application that has many parallel requests and all of these requests take a while until the server responds with the first byte it can happen that the server time says something high like 83s. The actual Page Load Time for the end user is probably faster as the browser downloads resources in parallel.

If you drill to the Purepaths you should see more than one PurePath for that page - is that correct? Not just the one that says 4 secs total in response time.

If you can - attach some screenshots of the performance report as well as of the purepaths

Let me give the context, We have few scenarios which has been identified as bottle neck areas, So I ran this scenario 5 times. All the time lag and delay happens for the first Load, which literally too long.

I have attached the Browser report [ server and user experience] and multiple purepath snap shots. There is a lot action on the purepath section, so we want to ensure we are moving forward in the correct path.

Any chance you can export one of these PurePaths and attach it or send it to me?

Based on the PurePath it seems like some of the time is spent in compiling code in memory. Is it possible that you dynamically create classes? Depending on the quantity this could take a while. Another explanation would be that you just restarted the application and the .NET CLR loads these assemblies for the first time. If that is the case it should only be slow the first time but then should be fast as this loading is already done.

Anyway - you should focus on the hotspots on the Server-Side PurePath. If you want - feel free to export one of these PurePaths and I have a closer look at it

Thanks Andi for the reply. So you the time lag in response in server side purepath should be the real point of focus at this point of time. The logic of first time delay due to clr loading assemblies may be true but this much lag needs more investigation for sure. So do we take the browser reports into consideration, I understand the server side purepath itself is good enough for technical investigation but we are reporting browser reports in our findings also. I have attached the purepath for your perusal. Its in .xml format.

Thanks. It seems you attached the Export of the System Profile - but not of a PurePath. in order to export a PurePath simply right click on the PurePath in your PurePath dashlet and then select "Export". That will export that single PurePath into a .dts file.

If you want you can also export the whole Browser Action. Open the Browser Performance Report and right-click on the slow URL -> then select Export.

That helps. Just as I thought. It is all compilation time. You could look into pre-compiling these assemblies - that will definitely help. I suggest you talk with your engineers and let them know about this. They will know how to optimize this step

Thanks Andi for the response I would definitely want your view on another similar issue but I will post it on a separate thread if you like, the first time compilation and page load takes around 35Sec and subsequent call backs take 100 MS, first time when the load happens, we see a huge amount some clr level exceptions, which disappears in subsequent reloads also attached the dts file for quick reference have a look at the errors pleaseempL.JPG

Answer by
Andreas G.·
Oct 01, 2014 at 06:33 AM

If you look at this exception then you see that this comes from an XmlSchema Validator triggered when the System.Data.Entity.Core.Objects.ObjectContext is created the first time. I am not an expert on ADO.NET Entity Framework. But - I would double check with the engineers to see whether Visual Studio also shows them configuration issues with the data schema.

I do however believe that this is probably not a major problem. Exceptions like this after an apprestart are very common in any type of application.

You should look into some of the other exceptions. Best is to drill to the Exception dashlet. It seems that this page tries to include certain files that cannot be found on the filesystem