ASP.NET MVC by default ships with two view engines: Web Forms and Razor. When we are creating a new ASP.NET MVC application both are being included in the application startup. Even when you are working with Razor only ASP.NET MVC resolves named views by searching for files that match the Web Forms view engine's naming convention at first. What can we do to change that and reduce the time needed to return a view to the end user? Let's have a look!

There is a belief among many developers that JavaScript is very slow, and writing more code in it than it’s necessary may adversely affect the performance. I guess it’s partially true. Incompetent use of this language can indeed decrease the quality of the project and the performance itself. However, JavaScript is one of the most developing languages.I’ll show you a few examples that will prove that JavaScript engines do what they can to speed up your code. In my work I focus on Google’s open source Java...

Modelling load distribution One of the challenges we face during the performance test design is determining the load we should use. By the load here, I mean a number of concurrent users performing certain actions in System Under Test (SUT). Obviously, depending on the type of performance test applied, the load will alter, as we are testing system in search of different class of problems. This article attempts to describe the case in which we will try to simulate the anticipated high traffic in t...

Each SharePoint software engineer should know how to avoid query throttling by writing efficient queries, and designing appropriate list’s structure. The sections below provide practices and tips ensuring your ability to access many items. Additionally, they help to keep site operating smoothly. All information in this article applies to SharePoint Server 2010. SharePoint 2010 has introduced many new features. One of them is Resource Throttling - designed to avoid performance degradation that can occur w...

When working with applications that utilize lots of threads and those threads arent particularry long running we can stumble upon a problem that we may lose most of the processing time for thread context switches, so it would be desirable to do all of the processing on a limited number of threads, usualy this can be done using a queue of delegates that each thread will process, but sometimes we cannot have that and still w...

Dlaczego w ogóle warto mierzyć wydajność zapytania SQL? Nie jeden raz zdarzyło mi się porównywać czasy wykonania dwóch różnych zapytań SQL które były rozwiązaniem jednego problemu. Nie zawsze w sposób jednoznaczny można określić, które z zapytań jest bardziej optymanlne.  W przypadku zapytań wykonywanych na instancji SQL Servera interesują nas następujące parametry czas wykonaniailość odczytów stron potrzebnych do wykonania zapytaniailość zapisów (np. w bazie tempdb)użycie czasu procesora Bardzo pomocny...