[18 Apr 2014 | No Comment | ]
Perceived Performance – Customer Driven Performance Testing

How to get the most from the performance testing? Performance testing could be laborious, fragile, complex process that requires special skills to get it up and running. It requires even deeper skills when interpreting the results especially when analyzing root causes of performance and scalability failures. How to get most of value of it with the available resources on a timely basis?
Start with the customer in mind. What would the customer perceive as an acceptable or delightful performance? Consider the following as a starting point.
Perceived Performance Key Ingredients

User stories. …

Read the full story »

Performance »

[11 Apr 2014 | 2 Comments | ]

Wouldn’t you want to know about problems earlier vs. later?How often one should perform performance testing? Is it once successful build is available? Is availability of a good build a trigger to run performance test?  What are other constraints and limitations should be taken into account when committing on a timeline? Let’s break it down to key parts.
Moving parts

Good Build. Normally a good build considered when it compiles without errors and passes basic functional tests. It may be sufficient for a monolith application, but it’s way far from sufficient for …

Performance »

[12 Mar 2014 | 2 Comments | ]

Here is my view what’s valued in software engineering, it’s crisp and it helps me gauging my impact. So here it is – you are valued when you either create value or reduce risk. Feature teams obviously create value by coding up the features that end users use and happily pay money for. As a performance engineer I am in the risk end of the house. I help identifying risk of having inadequate performance and scalability of the product. Bad performance leads to poor user experience, loss of trust in …


[26 Feb 2014 | No Comment | ]

This post outlines key components of ASP.NET MVC and their connections. This is helpful for those who are getting started with ASP.NET MVC especially to those who are transitioning from ASP.NET Forms.
RouteConfig.cs file is located in App_Start folder. It defines how to parse and route incoming requests based on the URL’s structure.
By default this is what it has:
url: "{controller}/{action}/{id}", defaults: new { controller = "Home",
                        action = "Index",
                        id = UrlParameter.Optional });

It means that if you app hosted on myApp.com domain then the …