لطفا منتظر باشید ...
• Table of Contents
• Index
Sams Teach Yourself Visual Studio® .NET 2003 in 21 Days
By
Jason Beres
Publisher
: Sams Publishing
Pub Date
: January 14, 2003
ISBN
: 0-672-32421-0
Pages
: 696
Sams Teach Yourself Visual Studio .NET in 21 Days will help developers that are new to application development and experienced developers understand how to use the .NET Framework and Visual Studio .NET to rapidly develop any type of computer application. The Visual Studio .NET development environment is the most comprehensive developer tool ever created, putting that together with the .NET Frameworks' Class Libraries, the developer has everything he or she needs to get up-to-speed on Microsoft's latest revolution in application development. This book will guide the developer through using the VS .NET IDE, the Visual Basic .NET and C# language, and the supporting tools available from Microsoft to create Windows and Web-based applications. The market is full of books that pretty much say the same thing, which is already available in the help files, the author of this book has written and deployed over a dozen successful applications using Visual Studio .NET and the .NET Framework. All of his expertise and experience is used to give you the most comprehensive title on using Visual Studio .NET.
Understanding the ACT Test Results
There are Table 19.1.Page timings can be useful in determining the effect of either page coding or underlying database operations and caching. In the reports, this is primarily determined by looking at the TTFB (Time To First Byte) and TTLB (Time To Last Byte).Noting these times and making changes to the logic or database access gives you a good way to track the resulting changes and make sure that you haven't introduced a delay you didn't mean to!The performance counters for this testing, and many system problems as well, provide a wealth of information. The performance counters enable you to find when your clients and/or servers have reached their peaks in terms of processor, memory, disk I/O, and network throughput.The idea is that you should make sure that the testing isn't bottlenecked by the client computer that's driving the testing. If the client computer CPU usage is above 90%, it's probably the limiting factor in being able to produce a load on the Web server.By looking at various counters on the Web server, you should be able to determine performance issues. A rule of thumb is that the Web server CPU usage should be at least 80%. At that point, you'll see the maximum limit of the Web server and not the limitations of the client test computer.Comparing RPS on various test runs will help you tune the Web server and the Web application.
