Last post Sep 23, 2016 03:26 PM by bruce (sqlwork.com)
Sep 17, 2016 05:49 AM|aammi|LINK
So the title describe my confusion state and here is the situation.
I am working on the visual studio 2015. The solution that i have it has multiple projects and few of them are on asp.net where as 4 new projects are on angular js. So far application was running fine and we had no issue.
I used the cache object in C# to preserver the server data on the browser to load the dropdown to save the trip. Now we are using AngularJs as. When I am arriving the landing page of the anjular js. It takes 45 to 1 minutes to load the page first time.
Next time the page take 6 seconds. However it gets bad after 30 minutes or so Looking into fiddler I found that all the files in the index page is being loaded and thus we are seeing the performance issue. for the first time. So now i have few question.
1) is there a way to limit the load of the files at the landing page. I understand it is a single page application but it there might be way.
2) The issue occur after 30 minutes or an hour later. Should I be caching the files for longer time maybe for a week or 15 days?
3) Would it cause toehr issues it the files are saved for 15 days.
4) In visual studio, i read some article tto configure cache webconfig file for client side caching. It is output cache.
5) I assume output cache is not for the webform only but for any client content. http, css file.
6)controllerJs and other Js file can also be saved in cache? Ar they consider static?
5) So what is http cache and when it should be use. When the output cache should be used?
8) If i cache the content file for example 'myfile.js' and it is cache. now whne i update the 'myfile.js' will the change take place and how?
Note: I do not want to update the IIS settings because we release our product as exe to the client.
Now working on the Anjuar js
Sep 21, 2016 12:39 PMemail@example.com|LINK
Could you please tell me why your page load takes so much time?
Many js file need to load or need to load data?
Know the reason firstly, then we could find the solution
Sep 22, 2016 05:06 AM|aammi|LINK
Well, we have a single page application and when the page loads for the first time it gets 200 files and it takes around 40 seconds. In the subsequent request without closing or signing out from the application not all the pages loads again and it takes
only 6 seconds. However, when user comes back by after 20 or 30 minutes login again, all the pages loads again. so where does the cashing goes?
I did the caching from the C# where some data would be saved in the client side. In the subsequent request, parameter would match and if the same then page fetch the data from the client side, browser, I assume.
But it was not the output cache because output cache saved in the server side. So where that output cache could have been useful?
Sep 23, 2016 03:26 PM|bruce (sqlwork.com)|LINK
most likely its not caching, but asp.net recycle. if not used for 20 minutes, asp.net shuts down, which also clears any asp.net server caches. after shutdown, the next request restarts the app pool. depending on the number and complexity of the dll's in
the bin folder, this can take a while (40 seconds is actually a pretty fast startup).
you change the recycle timeout, but there can be other causes. if you want your site to always be running, the most common method is a timer job that ping the site every couple minutes.