Last post May 02, 2012 03:43 PM by bbcompent1
May 01, 2012 06:59 AM|rakesh121189|LINK
Is there any way i can deploy asp web application on multiple systems or multiple iis enabled windows xp systems.
since the application is running very slow when used by around 80 + people...
May 01, 2012 08:22 AM|bbcompent1|LINK
You might be able to do something with Microsoft's free load distributor, I forget the name but what you can do is you place several web servers in a pool and the software sends the requests in a round robin format.
May 01, 2012 08:23 AM|bbcompent1|LINK
Its MS Application Request Routing:
May 01, 2012 09:00 AM|rakesh121189|LINK
could you please explain how do i use the application
i am using the default iis services available on the windows xp system SP3
and i want to deploy the application in such a way that when the system is overloaded the application redirect the users to different server but when updating any information on the database it should get replicated on both servers i am really not good at
this as this is the first time i have created a web application.. Please help
May 01, 2012 10:00 AM|bbcompent1|LINK
You probably would get better guidance on this subject over at the IIS forums since we don't cover advanced IIS configuration on the asp.net forums. They do have videos out there that teach how to use it and configure it.
May 01, 2012 12:14 PM|tmorton|LINK
Have you determined where your bottlenecks are? If the slowness comes from the database layer, adding multiple web servers will not help you.
May 01, 2012 12:25 PM|bbcompent1|LINK
I'm with Terri on this one. 80 or so users shouldn't cause the site to drag that much. What do your queries look like? Post them here if you can.
May 02, 2012 01:14 AM|rakesh121189|LINK
i'm sure its the database cause every combobox on the page is connected to a datasource and on a page there are around 10+ and how much of of difference will it make if the vb code is written on vb file rather than using vb script on the aspx page
May 02, 2012 06:28 AM|bbcompent1|LINK
Are you using AJAX? If so, that can cause web applications to suffer if the viewstate gets too large. The visual advantage of the screen not flickering between postbacks don't outweigh the increased loading times.
May 02, 2012 12:38 PM|rakesh121189|LINK
the usage of ajax toolkit is very high ....
May 02, 2012 03:43 PM|bbcompent1|LINK
To see the size of your viewstate, fire up Fiddler which can diagnose the communication between server and browser. Check your viewstate. If its larger than 100K, that is going to cause excessive drag in some instances. The key thing to remember is this
problem will not present itself in development as there is no lag time between requests. However, you will see this behavior on production. One application I was working with (not my development) actually had a viewstate that was over 1 megabyte. I would hit
my dropdown list, wait 15-20 seconds and then it would finally respond. You might want to use JQuery instead of AJAX with that many controls counting on the partial postback.