Book Image

Mastering C# Concurrency

Book Image

Mastering C# Concurrency

Overview of this book

Starting with the traditional approach to concurrency, you will learn how to write multithreaded concurrent programs and compose ways that won't require locking. You will explore the concepts of parallelism granularity, and fine-grained and coarse-grained parallel tasks by choosing a concurrent program structure and parallelizing the workload optimally. You will also learn how to use task parallel library, cancellations, timeouts, and how to handle errors. You will know how to choose the appropriate data structure for a specific parallel algorithm to achieve scalability and performance. Further, you'll learn about server scalability, asynchronous I/O, and thread pools, and write responsive traditional Windows and Windows Store applications. By the end of the book, you will be able to diagnose and resolve typical problems that could happen in multithreaded applications.
Table of Contents (17 chapters)
Mastering C# Concurrency
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Load testing and scalability


We see that both the controllers have behaved the same so far. However, what about scalability? To check how well the application scales, we need to have many requests from many users. We will be able to do this with the help of different tools. First, we can use Visual Studio, but it requires the Ultimate edition (or the Enterprise edition for Visual Studio 2015) where web test tools are available. If you have it, then you can create a new project and choose the Web Performance and Load Test project from the test category. In the samples folder, there is an already created test project that is called AsyncServerTests. Now we need to create Web Performance Test. After creating, it will run in the browser and try to record your test. You can record it from the browser or stop the recording and add a new request as shown in the following screenshot; then in Properties provide a full URL to see what have we tested so far:

Next, we need to create a load test. When...