Tech Notes

You have gathered requirements from clients, identified key critical business scenarios, analyzed the workload distributions, found out performance goals and requirements, identified  tool for generating load, setup the test environment, designed the scripts, executed the performance run, collected the raw data, analyzed it, what next?  Send information to stakeholders? No!!  Wait!! It needs to formatted, customized for different stakeholder(s) and reported accordingly. This article suggests one of the ways to report performance run results to client especially if the performance testing activity has been outsourced to yours company.  It discusses the performance report template and importantly the reasons for including the items in the report. The performance report template contains information by data collected from client side only and doesn’t discuss / talk about data from server side like processor utilization etc. Broadly the performance report has been divided in three major

It’s not something new today to know that performance of the web application needs to be taken seriously by all stakeholders before releasing it to their customers.  The performance of the application can be tuned either at back-end or at front-end.  One of the most important metric for end-user is ‘Web Page Load Time’ to gauge the performance of the web site. In this article, I have listed tips (best practices for web page optimization at front-end) gathered from different sources (references are provided at the end). The tips are categorized in following broad categories.  Some tips might belong to multiple categories.  In that case, tip is listed under a category, which impacts web page performance most.  Following are broader categories of best practices where all tips belong to – Optimization of Number of Network Round Trips Optimization of Network Latency (Network Related) Optimization of Network Latency (HTTP Request Size) Optimization of Network Latency (HTTP Payload Si

In ‘Single User Load’, web analyzer like HTTPWatch, DynaTrace etc. are used while browsing through the scenarios and page load time and various other KPIs are collected.  The KPIs are analyzed further for tuning the web page response time. Following are the key KPIs that can be used for analysis purpose – Web Page Loading Time Network Time HTTP Requests Request Size Web Page Loading KPIs Time to First Impression o         This is the time from when the URL is entered into the browser until the user has the first visual indication of the page that gets loaded.  It depends on the initial HTML document when the browser can start drawing content. There are different Best Practices available that talk about different strategies. Google for example downloads a minimalist page to provide fast first visual rendering. It then delays loads more content after ‘onLoad’ or even later when the user starts interacting with the page. o         The recommended value for this KPI is like this –