Hi, I'm working with a extremely high bandwidth sensible servers (more than a million pages views per day) and I want to know about the convenience of working with ASP.NET AJAX.
I've seen that everypage with ASP.NET AJAX downloads a JS file (webresource) of more than 80Kb (compressed)... and 80Kb x 1.000.000 = 80 Gb/day...
On the other hand, I know that the user experience is improved, but... what about the server performance?
I only want to know your experiencies on this way: bandwith and server performance with high charge servers.
Well, it's actually 3 files, totalling 134,473 KB, though I checked it w/o GZIP turned on, so I'm not sure how much you gain with it; one of the three doesn't have the whitespace, etc removed already. For argument's sake and round numbers, let's call it 100KB / page.
So, to your point, that's x 1,000,000 so you're looking at 100 GB/day. IF every one of those page loads is a unique user.
Don't forget, if a user navigates within your site, or has been to your site before, their browser should cache those js files and therefore they'd only get hit with that download the first time they come to your site or if they've cleared their cache.
Further, not only is user experience improved, but take a basic webform as an example. If you have a 8 KB page with a form on it, and the user submits said form, then on a normal postback the whole page is served again (all 8KB). If you wrap that form in an updatepanel, then only the form itself is served in response (probably something around 10% of the total page's markup, etc, once you strip out headers, script tags, other sections of the page, and so on). If you forego the updatepanel and write custom js that hits webservices and so on instead, you can potentially reduce it even further (having the web service respond with just the "Everything's great!" message, for example).
I've honestly not done an impact analysis on many small requests, vs. few big ones, so that's an open item for you to investigate, but from a bandwidth perspective, I think you're overall in better shape, unless you have a lot of visitors that are 'first time' visitors from the .js file download perspective.