Skip to main content

WPF - Binding of TextBox in a Grid

Today we will talk about WPF and how we improve the loading time of our window. One of my colleague started to have a performance problem with an application written in WPF. The application has to run on some virtual machines with Windows and .NET 3.5
The application has a window with a grid that contains 200 cells. The model behind the view has an object with 50 property. I know we have too many properties, but this is the model, we need to optimize the loading time of the page and not to make a review.
public class MyModel : INotifyPropertyChanged
{
  public Foo Obj1 { get;  set ...}
}
public class FooModel : INotifyPropertyChanged
{
  public string P1 { get; set ... }
  public string P2 { get; set ... }
  ...
  public string P50 { get; set ... }
}
This model is bind to a grid that contains 4 columns and 50 rows. Each property is bind 4 times to the cell controller. The controller of the cell is a simple TextBox (this is a sample code).  The grid is similar to this:
                   <Grid>
                        <Grid.RowDefinitions> …  </Grid.RowDefinitions>
                        <Grid Grid.Row="0" Grid.Margin="10">
                            …
                            <TextBox Text="{Binding Path=DataObject.P11}" Grid.Row="1" Grid.Column="1"></TextBox>
                            <TextBox Text="{Binding Path=DataObject.P12}" Grid.Row="2" Grid.Column="1"></TextBox>
                            …
This is a simple binding, but on a virtual machine, under .NET 3.5, the loading time of this window is around 5-6 seconds. We need to find out what is the cause of this problem. After creating a sample project with this problem we discovered the cause of the problem.
It seems that the binding itself is very slow. If we compile the sample project with .NET 4.0 the loading time decreases a lot. But we cannot migrate to .NET 4.0. This is not an option now.
We could try to bind the grid to our model and each cell would be bind directly to the property.
<Grid Source= “Binding Path = DataObject”>
     …
     <TextBox Text="{Binding P1}" Grid.Row="1" Grid.Column="1"></TextBox>
With this solution the performance is improved with ~1 second. We still have a problem, the windows is loading too slowly.
What we can do? The cause of the problem is the TextBox. The TextBox binding consumes a lot of resources.
Looking over the view we can replace the TextBox with a TextBlock. Running the application again and voila. The loading time of the page is under 1 second.  Before applying this solution we need to check if we need to have the text editable. The good news is NO DON’T NEED that option.
In our case, replacing the TextBox with TextBlock improved the loading time of the page with more then 5 seconds. If we need to have the text editable, then we could register to the click event and replace the TextBlock with a TextBox. To have the same UI, we added a border to the TextBlock also.
The things to remember from this story is to use the most simple and UI base controllers we need. We shouldn’t use a complicated UI controller if don’t need it. The more complicated they are, the more resources will need.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP