Tech Notes

Traditionally performance testing approach usually follows Identification of Key Scenarios, Setting up the Load Environment, Designing the Scripts, Generating load, Monitoring and at last Analysis and Reporting.   It works for most of the system but it is completely a different ball game when conducting performance testing of large scale distributed system.   In this article, some of the key characteristics and challenges will be discussed for performance testing of large scale distributed system. Key Characteristics High Volume »         Terabyte of transactional records in database »         Network throughput in gigabits per second High Transactions »         Millions of transactions per second from end users »         Millions of transactions in database due to few triggers (e.g. large report generation due to batch processing) High Concurrency »        

When you run a server system, default settings might not meet the performance requirements of business needs.  For example, for some business needs lowest energy consumption is preferred and for others it could be low latency and high throughput.  This article will provide pointer to some of the common configuration parameters associated with processor & network of the Windows 2012 server. Processor Power Management Performance Boost Mode »         The default value for Boost mode is 3 i.e. Efficient Enabled »         Turbo is enabled for High Performance power plans on all Intel and AMD processors and it is disabled for Power Saver plans Minimum and Maximum Performance State »         Processors change between performance states (“P-states”) very quickly to match supply to demand, delivering performance where necessary and saving energy when possible »         Alter this setting if your server has spec