Question

what are the measures which reflects a highly scalable and with high performance asp.net form.

like time in seconds to load the page?

time in seconds to do data actions like Add delete.

page size.

Answer 1

This is a very open ended question. Performance and scalability can mean a whole host of different things. Serving a page quickly, or having it render in the browser quickly, is just one aspect of this. Tools such as Fiddler, YSlow etc can help you look at the time it takes a page, and all its assets (images, scripts etc) to get to the browser and become useful to the user, but this won’t tell you whether your site can serve 10s, 100, 1000s or millions of users.

To determine the scalability of your site you need to start looking at profiling tools, such as those that ship in VS.NET. You’ll be looking at numbers such as requests per second, CPU load, disk saturation. Generally, you’ll want to understand what your scale unit is – how many users each of your servers can support at some given load (e.g. 80% CPU) before you need to go buy another server.

Finally, your system isn’t scalable if you can’t add new servers, or add new resources to your existing server (e.g. memory disk), to see an improvement. You need to know that your architecture supports being scaled out or scaled up.

If I were you I’d…

1. Define what acceptable performance means for you (how long you want users to wait for a page, how long it should take to perform an action etc)
2. See if you’re hitting those requirements in the browser by measuring using the tools mentioned (Fiddler, YSlow etc).
3. Put your system under load using tools such as VS.NET’s perf tooling and see where you’re spending time and CPU. Fix stuff as you see it.
4. Read stuff like this: http://highscalability.com/ and look at the strategies that other sites use to scale. Find ones that work for you and try them out.

update from your comments to other answers you appear to be concerned about HOW to you should time stuff.

To use Fiddler for performance measurements look at this: http://www.fiddler2.com/fiddler/Perf/

To use IE’s developer tools for measuring perf look here: http://msdn.microsoft.com/en-us/ie/aa740478

To use the Chrome developer tools look here: http://code.google.com/chrome/devtools/docs/overview.html

However, I really like Fiddler. Not only will it allow you to see performance, it can record the HTTP requests and then generate VS.NET Web Tests. This allows you to create a set of performance tests based upon real user interactions. As you change your code you can re-test and look for perf improvements.