So i'm new to AJAX and just installed the AJAX toolkit.
When i have tried to used any of the object there my page are really slow, it like the server is forever to compile the site and when that is done the browser shows it in a flash.
You can see here :
This is not a problem when using only ASP.NET.
When i debug in VS2008 i can see that is looking for some random files when compiling like C:AjaxBuildAjaxServerAjaxControlToolkitToolkitScriptManagerToolkitScriptManager.cs and alot of other stuff, it goes through alot of setting there and i think that is the hold up, why it's so slow.
I have Sp1 installed, running Windows 7 64bit.
These pages are very small and standard. I basicly drag a toolkitscriptmanager, htmleditor, textbox and two buttons to the form. There isnt more.
This is the code for the first page :
The host has AJAX support and has installed SP1 for .NET.
I'm using PopupControlExtender in a GridView, which pops up various dropdowns, treeviews, calendars etc. depending on which cell is clicked. I'm populating the dropdowns on the OnPreRender event. The result is, GridView is becoming extremely slow. I've tried removing Calendar controls, the Grid is still very slow. My guess is the enormously large source view of the page, resulting from populating controls on PreRender. Here is a sample ItemTemplate:
My goal is to populate the controls inside popup panel only when that panel becomes visible. I tried using OnResolveControlID event for this in PopupControlExtender. But strangely enough, that event fires only when control is NOT found, contrary to what its name suggests.
Anyway, my goal is to populate the popup panels controls (mainly ListControls) ONLY when their container panel becomes visible - hoping that this will make the grid faster. The same grid works perfect with AutoGenerateColumns=true and no populating of ListControls (not an option). Also, I'm NOT using debug option in web.config.
I am using AUtomapper which I am very impressed with however, I have a complex object with many nested collections. I'm using Telerik OpenAccess and it returns the 1400 records fast but when I pass it to Automapper and it slows to a ridiculous crawl. Here is my code for reference:
I have a situation where I need to have close to 30 drop down lists on one form. The user also wants the autocomplete functionality. I decided to use the ASP.NET AJAX control. So that the page will load faster I hide them until they are needed. But, as more and more become visible the postback time is getting longer and longer.
I know this can be fixed, but I'm not sure how. Can anyone give me any advice, point me to some articles? Do you have a suggestion for another method of doing what I need? Maybe, I shouldn't even be using ComboBoxes for this?
Currently the page load slow. I am thinking of using JQuery load and render List<A> and List<B> separately and asynchronously. Can I still use MVVM pattern? Or I had to create to controller methods returning List<A> and List<B> separately?]
Page B - loads slowly and needs to do some CPU-intensive operations on the web server.
I noticed that when someone is loading Page B, then Page A also loads slowly. This is even worse if multiple users are loading Page B at the same time. Page A won't finish loading until Page B is done.
Is there a best practice for making sure that Page A can still load quickly? Maybe a config setting or IIS setting that I need to change from its default? With 2 users loading Page B at the same time, the web server CPU usage only gets to 30% so I suspect it might be something I can tweak with the settings.
I'm writing a simple web site using codebehind for each page, however using the "codefile" directive, not "codebehind" as such, because I'm not precompiling. I'm just using a text editor to edit the aspx and codebehind files. Problem is, every time I make a change to the code or the aspx file, and refresh the page in the browser, it takes a 2 or 3 seconds to come up the first time, like it's doing an on-demand initial compile. I assume that's what it's doing, as after the initial load, the page refreshes without any delay at all.
This behaviour is quite frustrating when making small changes to the html or code. I'm coming from classic ASP, where you could edit-refresh-edit-refresh etc. all day without your "stride" being broken by waiting for a "compile", you know? So I'd love to know if there's a setting which prevents this initial delay. When I want to deploy, I can do a compile or something, but while making lots of small edits, I just need the page to run without that initial delay.
I've developed a web page Client.aspx that is used for editing a client. This application has been deployed and I made sure that debug='false'.Upon selecting a client from the dropdownlist, his/her information is retrieved for editing. This retrieving process is very slow( about 9 seconds).Except this DropDownList, all the other controls on this page are within the Update Panel. There are 2-3 other Update Panels within the main Update Panel.
We recently migrated to v4 of .net. We are running iis 7 in integrated mode. When the site first starts its slow. I get that - it compiles for the first time. The odd thing is then we will go to certain pages and it seems to compile again. The next time i go that page its very fast. Nothing exceptional with the second page - but once that is hit the rest of the site is fast.
Every now and then (always after a long period of idle-time, e.g. overnight) when I access a site built using asp.net - it takes around 15 seconds to load the page (15 seconds before I see any progress whatsoever, then the page comes up fast).Further pages on that site, or refreshes, are quick as usual - they are also fast on other machines, only the first one seems to take the 'hit'.
Page tracing never through anything up (whole cycle was a fraction of a second) So my question is where else should I be looking? Perhaps IIS? Or could it still be my asp.net app and I'm just looking in the wrong place (the trace) for clues?As I don't have much control over the IIS server, anything I can check through asp.net would be more helpful, before I go ask that particular admin.
The first time that my page loads (this is after it has been deployed), it is terribly slow.
My guess is that it is still compiling dynamically, and not precompiling.When I publish through VS2008 I have "Allow this precompiled site to be updatable" unchecked and "Use fixed naming and single page assemblies" checked.Could I be missing something in my web.config file?
I can post the URL of the site if you would like to view it, but it takes 10+ seconds to load upon first visiting, and then less than 1 second to navigate the site.
I have a simple web application that loads very slow the very first time after i deploy it. I am using ASP.NET 3.5 SP1 / VS 2008 / Linq / Web forms to load the default.aspx home page. It is a very light page with nothing too fancy.Now to debug this load issue, I logged all the events in the global file and got the following log text:
Now my question is, between the Application_AuthenticateRequest and Session_Start functions, there is generally around 10 - 15 seconds - which i believe seems to be the problem.The thing, I am unsure why this is slow between these two functions.I am not using any forms authentication.Also, I am not doing anything fancy in the global file besides setting a session variable.
Page A loads very fast; Page B loads very slowly and does some CPU-intensive things on the web server. I noticed that if someone is loading Page B, then Page A also loads slowly - for ALL users. What is the standard practice for making sure this doesn't happen? If multiple users are loading Page B at the same time then Page A is ridiculously slow. Is there an IIS setting, web.config setting, or hardware configuration I could use to make sure that the fast-loading pages aren't bogged down by other pages that need more time to load?
We have an asp.net website running on IIS 6 Windows 2003. When ever we upload a class file to the App_Code folder our whole site goes down temporarily until, what I assume, compilation is complete. Has anyone else experienced this? Any other file we upload it does not do this only our class files.
Over the last week I've been investigating an issue for one of our clients whereby the initial page load following a deployment of their website takes around 1 minute, resulting in unacceptable downtime for end users. This was happening not only for code deplyments (bin dll's and .config files) but also if there were large numbers of .aspx pages updated. For code deployments it's not an issue, but for aspx updates it is; in this particular scenario, we are making use of a 3rd party content management system (RedDot from OpenText) in which every page of the site is published out as a distinct .aspx page. This means that for this website there's somewhere in the region of 2,400 separate .aspx pages. I realise this isn't an ideal situation but we're working within the constraints of the CMS, and we managed to correlate the instances where the site was unresponsive with App pool restarts, which also corresponded to publications of of .aspx pages.
I found an article by Tess Ferandez [URL] which describes all the reasons why the app pool may restart, and it does seem that if more than 15 .aspx pages are changed then the app pool will recycle and the pages will be re-compiled. Another msdn article [URL] then gave me a few pointers on how to start addressing this problem, and for the moment I've set a flag on the compilation options to prevent batch compilation:
This means that the initial page load now takes around 6 seconds instead of 1 minute, which is a great improvement. However, I also used the "Compilations Total" performance counter to investigate the number of pages that have been compiled by ASP.NET for my site and was quite surprised that the total number of pages that get compiled peaks at 44, which is odd given that there are 2,400 aspx pages in the site. If the batch flag is set to false, the counter slowly increments by 1 page at a time as you click around on the site; if batch mode is true, the initial compilation takes the number straight to 44 over the course of ~60 seconds. What I'm really struggling to understand is why all 2,400 pages aren't compiled. Does anyone have any inside info on what might be going on as all the documentation I've read seems to indicate that all of the pages should be compiled and this counter should be much higher.
for some reason when i view it in IE the page scrolling is extremely choppy. When i view it in firefox or safari the site is really smooth.I am not sure if i added somthing which made IE choppy because i do not remember it being choppy.... but i never really paid attention until i started to notice it.Is scrolling the site in IE choppy for you also?I tried to remove all the jquery and java - scripts i had, still choppy when scrolling. I'm not sure whats going on? The website is quite image heavy, even backgrounds are quite big, however firefox and safari have not problems... is it a IE chaching problem?