Fastest Bulk Inserts

Fastest universal way to insert data using standard ADO.NET constructs Now that the slow stuff is out of the way, lets talk about some hardcore bulk loading. Aside from SqlBulkCopy and specialized constructs involving ISAM or custom bulk insert classes from other providers, there is simply no beating the raw power of ExecuteNonQuery() on a parameterized INSERT statement.


 
internal static void FastInsertMany(DbConnection cnn)
{

  using (DbTransaction dbTrans = cnn.BeginTransaction())

  {

    using (DbCommand cmd = cnn.CreateCommand())

    {

      cmd.CommandText = "INSERT INTO TestCase(MyValue) VALUES(?)";

      DbParameter Field1 = cmd.CreateParameter();

      cmd.Parameters.Add(Field1);

      for (int n = 0; n < 100000; n++)

      {

        Field1.Value = n + 100000;

        cmd.ExecuteNonQuery();

      }

    }

    dbTrans.Commit();

  }

}

Simple, elegant, clean.  100,000 inserts on my machine in 1.4 seconds.  Yes, that’s 10 times more inserts than the DataAdapter/DbCommandBuilder/DataTable method, and at very nearly the same speed as example 1!

Do not, under any circumstances, bulk insert data by building your own command text over and over and over again.  That is the surest way to drag performance into the dirt.  Build your CommandText one time, build your parameters one time, and set their values over and over and over instead.  SQLite runs much faster, SQL Server runs much faster, and every database known to mankind will run much faster with a prepared, parameterized insert statement.

source: Fastest Bulk Inserts

How To: Scale .NET Applications

Overview
Scalability refers to the ability of an application to continue to meet its performance objectives with increased load. Typical performance objectives include application response time and throughput. When measuring performance, it is important to consider the cost at which performance objectives are achieved. For example, achieving a sub – second response time objective with prolonged 100% CPU utilization would generally not be an acceptable solution.
This How To is intended to help you make informed design choices and tradeoffs that in turn will help you to scale your application. An exhaustive treatment of hardware choices and features is outside the scope of this document.
After completing this How To, you will be able to:

  • Determine when to scale up versus when to scale out.
  • Quickly identify resource limitation and performance bottlenecks.
  • Identify common scaling techniques.
  • Identify scaling techniques specific to .NET technologies.
  • Adopt a step-by-step process to scale .NET applications.
  • Scale Up vs. Scale Out

    There are two main approaches to scaling:
    Scaling up. With this approach, you upgrade your existing hardware. You might replace existing hardware components, such as a CPU, with faster ones, or you might add new hardware components, such as additional memory. The key hardware components that affect performance and scalability are CPU, memory, disk, and network adapters. An upgrade could also entail replacing existing servers with new servers.
    Scaling out. With this approach, you add more servers to your system to spread application processing load across multiple computers. Doing so increases the overall processing capacity of the system.

    Pros and Cons
    Scaling up is a simple option and one that can be cost effective. It does not introduce additional maintenance and support costs. However, any single points of failure remain, which is a risk. Beyond a certain threshold, adding more hardware to the existing servers may not produce the desired results. For an application to scale up effectively, the underlying framework, runtime, and computer architecture must also scale up.

    Scaling out enables you to add more servers in the anticipation of further growth, and provides the flexibility to take a server participating in the Web farm offline for upgrades with relatively little impact on the cluster. In general, the ability of an application to scale out depends more on its architecture than on underlying infrastructure.

    When to Scale Up vs. Scale Out
    Should you upgrade existing hardware or consider adding additional servers? To help you determine the correct approach, consider the following:

  • Scaling up is best suited to improving the performance of tasks that are capable of parallel execution. Scaling out works best for handling an increase in workload or demand.
  • For server applications to handle increases in demand, it is best to scale out, provided that the application design and infrastructure supports it.
  • If your application contains tasks that can be performed simultaneously and independently of one another and the application runs on a single processor server, you should asynchronously execute the tasks. Asynchronous processing is more beneficial for I/O bound tasks and is less beneficial when the tasks are CPU bound and restricted to a single processor. Single CPU bound multithreaded tasks perform relatively slowly due to the overhead of thread switching. In this case, you can improve performance by adding an additional CPU, to enable true parallel execution of tasks.
  • Limitations imposed by the operating system and server hardware mean that you face a diminishing return on investment when scaling up. For example, operating systems have a limitation on the number of CPUs they support, servers have memory limits, and adding more memory has less effect when you pass a certain level (for example, 4 GB).
  • Load Balancing
    There are many approaches to load balancing. This section contains a discussion of the most commonly used techniques.

    Web Farm
    In a Web farm, multiple servers are load balanced to provide high availability of service. This feature is currently only available in Windows® 2000 Advanced Server and Datacenter Server. Figure 1 illustrates this approach.

    Load balancing in a Web farm

    Load balancing in a Web farm

     

    for more see: http://msdn.microsoft.com/en-us/library/ms979199.aspx

    Performance Comparison: .NET Remoting vs. ASP.NET Web Services

    Introduction

    ASP.NET Web services and .NET Remoting provide a full suite of design options for cross-process communication in distributed applications. In general, ASP.NET Web services provide the highest levels of interoperability with full support for WSDL and SOAP over HTTP, while .NET Remoting is designed for common language runtime type-system fidelity and supports additional data format and communication channels. For more information, see ASP.NET Web Services or .NET Remoting: How to Choose.

    This article focuses on comparing relative performance of these techniques.

    ASP.NET Web Services

    ASP.NET provides a Microsoft® IIS-hosted infrastructure that supports industry standards such as SOAP, XML, and WSDL. Although.NET Remoting supports IIS hosting and SOAP over HTTP, ASP.NET is designed to provide the highest level of SOAP interoperability including support for SOAP Section 5 and document/literal.

    ASP.NET can leverage the features available with IIS, such as security and logging. IIS hosting is also robust in that it will re-spawn Aspnet_wp.exe if it terminates. Also, ASP.NET Web services are much easier to create and consume than services exposed using .NET Remoting because configuration is simplified both at the server and client.

    For more details, see Building XML Web Services Using ASP.NET in the .NET Framework Developer’s Guide.

    .NET Remoting

    .NET Remoting is more versatile and extensible in terms of enabling communication between objects using different transport protocols and serialization formats. TCP, HTTP, and custom protocols are supported as are Binary, SOAP, and custom formats. Multiple-object creation and lifetime modes are supported including Singleton, SingleCall, and Client-Activated. Remoting requires a host process, which can be IIS, or a Microsoft® Windows service or executable written in .NET.

    A .NET Remoting object using the SOAP formatter can be exposed as an XML Web service when hosted in IIS with ASP.NET. Since the payload is encoded in SOAP over HTTP, any client that supports the SOAP Encoding format can access the objects over the Internet. Another advantage of using the HTTP protocol is that it generally passes unobstructed across most firewalls. The TCP channel and the Binary formatter can be employed in an intranet environment where both the server and client are running on the .NET Framework. This approach is optimized for performance since raw sockets are used to transmit data across the network using a custom protocol that is more efficient than HTTP. Though this approach offers excellent performance in a closed environment, it cannot be employed in cross-platform scenarios where the client is not running the .NET Framework.

    IIS hosting provides secure communication for wire-level protection using Secure Sockets Layer (SSL), and you can also leverage IIS and ASP.NET authentication and authorization. The TCP channel as well as the HTTP channel with non-IIS hosting do not support secure socket transmission, so data is transmitted in clear text. You are required to implement your own security if you are using the TCP channel or the HTTP channel hosted in processes other than IIS.

    For more details, please refer to the .NET Remoting Overview in the .NET Framework Developer’s Guide.

    Conclusion

    As these tests demonstrate, the various design choices available with ASP.NET Web services and .NET Remoting carry varying amounts of overhead and therefore have vastly different performance characteristics. The size of data being passed is also significant and multiplies the differences between the other design choices. This comparison covers only stateless, synchronous remote procedure calls and does not cover the performance implications of authentication, authorization, and data privacy, which are other significant factors affecting the performance of distributed applications.

    Though both the .NET Remoting infrastructure and ASP.NET Web services can implement inter-process communication, each is designed with a particular level of expertise and flexibility in mind to benefit a different target audience. If your application needs interoperability with other platforms or operating systems, you would be better off using ASP.NET Web services, as they are more flexible in that they support SOAP section 5 and Document/Literal. On the other hand, use .NET Remoting when you need the richer object-oriented programming model. See ASP.NET Web Services or .NET Remoting: How to Choose for details. In scenarios where performance is the main requirement with security and process lifecycle management is not a major concern, .NET Remoting TCP/Binary is a viable option; however, keep in mind that you can increase the performance of IIS-hosted implementations by adding a few more machines into the system, which may not be possible when using a .NET Remoting TCP/Binary implementation.

    (sursa: http://msdn.microsoft.com/en-us/library/ms978411.aspx)

    Improving Managed Code Performance

    The CLR consists of a number of components that are responsible for managed code execution. These components are referred to throughout this chapter, so you should be aware of their purpose. Figure 5.1 shows the basic CLR architecture and components.

    CLR architecture

    CLR architecture

    The way you write managed code significantly impacts the efficiency of the CLR components shown in Figure 5.1. By following the guidelines and techniques presented in this chapter, you can optimize your code, and enable the run-time components to work most efficiently. The purpose of each component is summarized below:

    JIT compiler. The just-in-time (JIT) compiler converts the Microsoft intermediate language (MSIL) that is contained in an assembly into native machine code at run time. Methods that are never called are not JIT-compiled.
    Garbage collector. The garbage collector is responsible for allocating, freeing, and compacting memory.
    Structured exception handling. The runtime supports structured exception handling to allow you to build robust, maintainable code. Use language constructs such as try/catch/finally to take advantage of structured exception handling.
    Threading. The .NET Framework provides a number of threading and synchronization primitives to allow you to build high performance, multithreaded code. Your choice of threading approach and synchronization mechanism impacts application concurrency; hence, it also impacts scalability and overall performance.
    Security. The .NET Framework provides code access security to ensure that code has the necessary permissions to perform specific types of operations such as accessing the file system, calling unmanaged code, accessing network resources, and accessing the registry.
    Loader. The .NET Framework loader is responsible for locating and loading assemblies.
    Metadata. Assemblies are self-describing. An assembly contains metadata that describes aspects of your program, such as the set of types that it exposes, and the members those types contain. Metadata facilitates JIT compilation and is also used to convey version and security-related information.
    Interop. The CLR can interoperate with various kinds of unmanaged code, such as Microsoft Visual Basic®, Microsoft Visual C++®, DLLs, or COM components. Interop allows your managed code to call these unmanaged components.
    Remoting. The .NET remoting infrastructure supports calls across application domains, between processes, and over various network transports.
    Debugging. The CLR exposes debugging hooks that can be used to debug or profile your assemblies.

    Performance and Scalability Issues
    This section is designed to give you a high-level overview of the major issues that can impact the performance and scalability of managed code. Subsequent sections in this chapter provide strategies, solutions, and technical recommendations to prevent or resolve these issues. There are several main issues that impact managed code performance and scalability:

    Memory misuse. If you create too many objects, fail to properly release resources, preallocate memory, or explicitly force garbage collection, you can prevent the CLR from efficiently managing memory. This can lead to increased working set size and reduced performance.
    Resource cleanup. Implementing finalizers when they are not needed, failing to suppress finalization in the Dispose method, or failing to release unmanaged resources can lead to unnecessary delays in reclaiming resources and can potentially create resource leaks.
    Improper use of threads. Creating threads on a per-request basis and not sharing threads using thread pools can cause performance and scalability bottlenecks for server applications. The .NET Framework provides a self-tuning thread pool that should be used by server-side applications.
    Abusing shared resources. Creating resources per request can lead to resource pressure, and failing to properly release shared resources can cause delays in reclaiming them. This quickly leads to scalability issues.
    Type conversions. Implicit type conversions and mixing value and reference types leads to excessive boxing and unboxing operations. This impacts performance.
    Misuse of collections. The .NET Framework class library provides an extensive set of collection types. Each collection type is designed to be used with specific storage and access requirements. Choosing the wrong type of collection for specific situations can impact performance.
    Inefficient loops. Even the slightest coding inefficiency is magnified when that code is located inside a loop. Loops that access an object’s properties are a common culprit of performance bottlenecks, particularly if the object is remote or the property getter performs significant work.

    (sursa: http://msdn.microsoft.com/en-us/library/ms998547.aspx)

    ASP.NET Performance Monitoring, and When to Alert Administrators : http://msdn.microsoft.com/en-us/library/ms972959.aspx

    Set Performance Objectives

    Your project goals must include measurable performance objectives. From the very beginning, design so that you are likely to meet those objectives. Do not over-research your design. Use the planning phase to manage project risk to the right level for your project. To accomplish this, you might ask the following questions: How fast does your application need to run? At what point does the performance of your application become unacceptable? How much CPU or memory can your application consume? Your answers to these questions are your performance objectives. They help you create a baseline for your application’s performance. These questions help you determine if the application is quick enough.

    Performance objectives are usually specified in terms of the following:
    Response time. Response time is the amount of time that it takes for a server to respond to a request.
    Throughput. Throughput is the number of requests that can be served by your application per unit time. Throughput is frequently measured as requests or logical transactions per second.
    Resource utilization. Resource utilization is the measure of how much server and network resources are consumed by your application. Resources include CPU, memory, disk I/O, and network I/O.
    Workload. Workload includes the total number of users and concurrent active users, data volumes, and transaction volumes.

    You can identify resource costs on a per-scenario basis. Scenarios might include browsing a product catalog, adding items to a shopping cart, or placing an order. You can measure resource costs for a certain user load, or you can average resource costs when you test the application by using a certain workload profile. A workload profile consists of a representative mix of clients performing various operations.

    Performance Modeling

    Performance modeling helps you evaluate your design decisions against your objectives early on,before committing time and resources. Invalid design assumptions and poor design practices may mean that your application can never achieve its performance objectives. The performance modeling process model presented in this guide is summarized in Figure.

    Eight-step performance modeling process

    Eight-step performance modeling process

    The performance modeling process consists of the following steps:
    1. Identify key scenarios. Identify those scenarios in which performance is important and the ones that pose the most risk to your performance objectives.
    2. Identify workloads. Identify how many users, and how many concurrent users, your system needs to support.
    3. Identify performance objectives. Define performance objectives for each of your key scenarios. Performance objectives reflect business requirements.
    4. Identify budget. Identify your budget or constraints. This includes the maximum execution time in which an operation must be completed and resource utilization such as CPU, memory, disk I/O, and network I/O constraints.
    5. Identify processing steps. Break your scenarios down into component processing steps.
    6. Allocate budget. Spread your budget determined in Step 4 across your processing steps determined in Step 5 to meet the performance objectives you defined in Step 3.
    7. Evaluate. Evaluate your design against objectives and budget. You may need to modify design or spread your response time and resource utilization budget differently to meet your performance objectives.
    8. Validate. Validate your model and estimates. This is an ongoing activity and includes prototyping, testing, and measuring.

    Performance Counters for ASP.NET

    ASP.NET System Performance Counters
    ASP.NET supports the ASP.NET system performance counters listed in the following table. These counters aggregate information from all ASP.NET applications on a Web server computer.

    Note:
    There is a significant difference between the State Server Sessions counters found in the ASP.NET performance object, which apply only to the server computer on which the state server is running, and the Sessions counters found in the ASP.NET Applications performance object, which apply only to user sessions that occur in-process.

    Application Restarts
    The number of times that an application has been restarted during the Web server’s lifetime. Application restarts are incremented each time an Application_OnEnd event is raised. An application restart can occur because of changes to the Web.config file, changes to assemblies stored in the application’s Bin directory, or when an application must be recompiled due to numerous changes in ASP.NET Web pages. Unexpected increases in this counter can mean that problems are causing your Web application to recycle. In such circumstances you should investigate as soon as possible.

    Note:
    This value is reset to zero every time the Internet Information Services (IIS) host is restarted.

    Application Running
    The number of applications running concurrently on the server computer.

    Requests Disconnected
    The number of requests that have been disconnected due to a communication failure.

    Requests Queued
    The number of requests waiting for service from the queue. When this number starts to increment linearly with increased client load, the Web server computer has reached the limit of concurrent requests that it can process. The default maximum for this counter is 5,000. You can change this setting in the Machine.config file.

    Requests Rejected
    The total number of requests not executed because of insufficient server resources to process them. This counter represents the number of requests that return a 503 HTTP status code, indicating that the server is too busy.

    Request Wait Time
    The number of milliseconds that the most recent request waited in the queue for processing.

    Session State Server Connections Total
    The total number of session-state connections made to the computer on which out-of-process session-state data is stored. For more information, see Session-State Modes.

    Session SQL Server Connections Total
    The total number of session-state connections made to the Microsoft SQL Server database in which session-state data is stored. For more information, see Session-State Modes.

    State Server Sessions Abandoned
    The number of user sessions that have been explicitly abandoned. These are sessions that are ended by specific user actions, such as closing the browser or navigating to another site. This counter is available only on the computer where the state server service (aspnet_state) is running.

    State Server Sessions Active
    The number of currently active user sessions. This counter is available only on the computer where the state server service (aspnet_state) is running.

    State Server Sessions Timed Out
    The number of user sessions that have become inactive through user inaction. This counter is available only on the computer where the state server service (aspnet_state) is running.

    State Server Sessions Total
    The number of sessions created during the lifetime of the process. This counter is the total value of State Server Sessions Active, State Server Sessions Abandoned, and State Server Sessions Timed Out. This counter is available only on the computer where the state server service (aspnet_state) is running.

    Worker Process Restarts
    The number of times a worker process has been restarted on the server computer. A worker process can be restarted if it fails unexpectedly or when it is intentionally recycled. If this counter increases unexpectedly, you should investigate as soon as possible.

    Worker Process Running
    The number of worker processes running on the server computer.

    ASP.NET Application Performance Counters
    ASP.NET supports the application performance counters listed in the following table. These counters enable you to monitor the performance of a single instance of an ASP.NET application. A unique instance named __Total__ is available for these counters. This instance aggregates counters for all applications on a Web server (similar to the global counters described earlier in this topic). The __Total__ instance is always available. The counters will display zero when no applications are currently executing on the server.

    Anonymous Requests
    The number of requests that are using anonymous authentication.

    Anonymous Requests/Sec
    The number of requests per second that are using anonymous authentication.

    Cache Total Entries
    The total number of entries in the cache. This counter includes both use of the cache by the ASP.NET page framework and use of the application cache through cache APIs.

    Cache Total Hits
    The total number of hits from the cache. This counter includes both use of the cache by the ASP.NET page framework and use of the application cache through cache APIs.

    Cache Total Misses
    The number of failed cache requests per application. This counter includes both use of the cache by the ASP.NET page framework and use of the application cache through cache APIs.

    Cache Total Hit Ratio
    The ratio of hits to misses for the cache. This counter includes both use of the cache by the ASP.NET page framework NET and use of the application cache through cache APIs.

    Cache Total Turnover Rate
    The number of additions and removals to the cache per second, which is useful in helping to determine how effectively the cache is being used. If the turnover rate is high, the cache is not being used efficiently.

    Cache API Entries
    The total number of entries in the application cache.

    Cache API Hits
    The total number of hits from the cache when it is accessed only through the external cache APIs. This counter does not track use of the cache by the ASP.NET page framework.

    Cache API Misses
    The total number of failed requests to the cache when accessed through the external cache APIs. This counter does not track use of the cache by the ASP.NET page framework.

    Cache API Hit Ratio
    The cache hit-to-miss ratio when accessed through the external cache APIs. This counter does not track use of the cache by the ASP.NET page framework.

    Cache API Turnover Rate
    The number of additions and removals to the cache per second when used through the external APIs (excluding use by the ASP.NET page framework). It is useful in helping determine how effectively the cache is being used. If the turnover rate is high, then the cache is not being used effectively.

    Compilations Total
    The total number of compilations that have taken place during the lifetime of the current Web server process. Compilation occurs when a file with an .aspx, .asmx, .ascx, or .ashx file name extension, or a code-behind source file, is dynamically compiled on the server.

    This number will initially climb to a peak value as requests are made to all parts of an application. Once compilation occurs, however, the resulting compiled output is saved to disk, where it is reused until its source file changes. This means that even in the event of a process restart the counter can remain at zero (inactive) until the application is modified or redeployed.

    Debugging Requests
    The number of requests that occur while debugging is enabled.

    Errors During Preprocessing
    The number of errors that occurred during parsing, excluding compilation and run-time errors.

    Errors During Compilation
    The number of errors that occur during dynamic compilation, excluding parser and run-time errors.

    Errors During Execution
    The total number of errors that occur during the execution of an HTTP request, excluding parser and compilation errors.

    Errors Unhandled During Execution
    The total number of unhandled errors that occur during the execution of HTTP requests. An unhandled error is any run-time exception that is not trapped in user code and enters the ASP.NET internal error-handling logic. Exceptions to this rule occur when:

    Custom errors are enabled, an error page is defined, or both.

    The Page_Error event is defined in user code and either the error is cleared (using the ClearError method) or a redirect is performed.

    Errors Unhandled During Execution/Sec
    The number of unhandled exceptions per second that occur during the execution of HTTP requests.

    Errors Total
    The total number of errors that occur during the execution of HTTP requests, including any parser, compilation, or run-time errors. This counter is the sum of the Errors During Compilation, Errors During Preprocessing, and Errors During Execution counters. A well-functioning Web server should not generate errors. If errors occur in your ASP.NET Web application, they may skew any throughput results because of very different code paths for error recovery. Investigate and fix any bugs in your application before performance testing.

    Errors Total/Sec
    The number of errors per second that occur during the execution of HTTP requests, including any parser, compilation, or run-time errors.

    Output Cache Entries
    The total number of entries in the output cache.

    Output Cache Hits
    The total number of requests serviced from the output cache.

    Output Cache Misses
    The number of failed output-cache requests per application.

    Output Cache Hit Ratio
    The percentage of total requests serviced from the output cache.

    Output Cache Turnover Rate
    The number of additions and removals to the output cache per second. If the turnover rate is high, the cache is not being used effectively.

    Pipeline Instance Count
    The number of active request pipeline instances for the specified ASP.NET application. Since only one execution thread can run within a pipeline instance, this number gives the maximum number of concurrent requests that are being processed for a given application. In most circumstances it is better for this number to be low when under load, which signifies that the CPU is well utilized.

    Request Bytes In Total
    The total size in bytes of all requests.

    Request Bytes Out Total
    The total size in bytes of responses sent to a client. This does not include HTTP response headers.

    Requests Executing
    The number of requests currently executing.

    Requests Failed
    The total number of failed requests. Any status codes greater than or equal to 400 will increment this counter.

    Requests that cause a 401 status code increment this counter and the Requests Not Authorized counter. Requests that cause a 404 or 414 status code increment this counter and the Requests Not Found counter. Requests that cause a 500 status code increment this counter and the Requests Timed Out counter.

    Requests Not Found
    The number of requests that failed because resources were not found (status code 404 or 414).

    Requests Not Authorized
    The number of requests that failed due to no authorization (status code 401).

    Requests Succeeded
    The number of requests that executed successfully (status code 200).

    Requests Timed Out
    The number of requests that timed out (status code 500).

    Requests Total
    The total number of requests since the service was started.

    Requests/Sec
    The number of requests executed per second. This represents the current throughput of the application. Under constant load, this number should remain within a certain range, barring other server work (such as garbage collection, cache cleanup thread, external server tools, and so on).

    Sessions Active
    The number of sessions currently active. This counter is supported only with in-memory session state.

    Sessions Abandoned
    The number of sessions that have been explicitly abandoned. This counter is supported only with in-memory session state.

    Sessions Timed Out
    The number of sessions that timed out. This counter is supported only with in-memory session state.

    Sessions Total
    The total number of sessions. This counter is supported only with in-memory session state.

    Transactions Aborted
    The number of transactions canceled for all active ASP.NET applications.

    Transactions Committed
    The number of transactions committed for all active ASP.NET applications.

    Transactions Pending
    The number of transactions in progress for all active ASP.NET applications.

    Transactions Total
    The total number of transactions for all active ASP.NET applications.

    Transactions/Sec
    The number of transactions started per second for all active ASP.NET applications.

    (sursa: http://msdn.microsoft.com/en-us/library/fxk122b4.aspx)

    10 ASP.NET Performance and Scalability Secrets

    ASP.NET 2.0 has many secrets, which when revealed can give you big performance and scalability boost. For instance, there are secret bottlenecks in Membership and Profile provider which can be solved easily to make authentication and authorization faster. Furthermore, ASP.NET HTTP pipeline can be tweaked to avoid executing unnecessary code that gets hit on each and every request. Not only that, ASP.NET Worker Process can be pushed to its limit to squeeze out every drop of performance out of it. Page fragment output caching on the browser (not on the server) can save significant amount of download time on repeated visits. On demand UI loading can give your site a fast and smooth feeling. Finally, Content Delivery Networks (CDN) and proper use of HTTP Cache headers can make your website screaming fast when implemented properly. In this article, you will learn these techniques that can give your ASP.NET application a big performance and scalability boost and prepare it to perform well under 10 times to 100 times more traffic.

    In this article we will discuss the following techniques:

    • ASP.NET pipeline optimization
    • ASP.NET process configuration optimization
    • Things you must do for ASP.NET before going live
    • Content Delivery Network
    • Caching AJAX calls on browser
    • Making best use of Browser Cache
    • On demand progressive UI loading for fast smooth experience
    • Optimize ASP.NET 2.0 Profile provider
    • How to query ASP.NET 2.0 Membership tables without bringing down the site
    • Prevent Denial of Service (DOS) attack

    The above techniques can be implemented on any ASP.NET website, especially those who use ASP.NET 2.0’s Membership and Profile provider.

    You can learn a lot more about performance and scalability improvement of ASP.NET and ASP.NET AJAX websites from my book – Building a Web 2.0 portal using ASP.NET 3.5.

    (sursa: http://www.codeproject.com/KB/aspnet/10ASPNetPerformance.aspx)