The JetBrains Blog

The compound effect is when small changes executed consistently over time lead to dramatic results. It can go both ways, either enhancing the positives or aggravating the problems. Regular profiling, or lack thereof, is a good example of the compound effect. If you invest a little bit of time in …

Some memory issues are non-critical, but rather annoying. They occur once every couple of months and then disappear again. Of course, these annoying bugs only show up once an application is operating under production conditions. However, such problems can often be solved using a profiler. Shyam Sund…

You can develop fairly efficient applications straight away without a profiler, but if you work with third-party code via API, then bottlenecks will occur quite often. It is impossible to predict, but it is still possible to account for third-party code specifics without having the code itself. One …

Today, we would like to share a few user stories about using the dotTrace performance profiler. We will tell you how a flaw was found in the new Intel CPUs' architecture, as well as how to find application performance problems when testing in the conventional sense is impossible. We’ll also share so…