Version 2020.2 EAP01 finally brings dotMemory to Linux and macOS! For these systems, dotMemory is currently available only as a command-line tool. The tool is free and lets you take and save memory snapshots. To analyze the snapshots, you still need the standalone version of dotMemory, which is only available on Windows. What you can profile Here's the dotMemory compatibility list for Linux and macOS: (more…)

It seems that a common problem among profiling tools (including ours) is that they require too much effort from a developer. Profiling currently is seen as some kind of a last resort for when something has gone horribly wrong. The use of profilers is very episodic and chaotic, and it's quite often ineffective because you simply can't be an expert in a tool you use only once every six months. We find this kind of sad because we strongly believe that regular profiling is essential for product quality. That being said, is there any solution? Well, our answer is "yes," but with some caution. Si

A little over a year ago, we ran a series of blog posts describing performance improvements we were making to ReSharper. We’ve delivered a lot of improvements in the releases since then, but we haven’t yet delivered on the big one - running ReSharper out of process. We thought it was about time we gave you an update on where we are. TL;DR: This isn’t an announcement post. We don’t have an ETA to share right now, although we have made significant progress on what is a massive problem. This post should give you an idea of the scale of the technical challenges we are working through in order to

In today’s blog post, we’ll take a look at the new Profiler features of GoLand. We will split this article into two sections: · General profiler usage in which we’ll cover the common features of the profiler across the various profiler methods. · Using the different profiling methods in which we’ll cover how to use each individual profiling method and share code samples so you can try this on your own computer. (more…)

Back in Rider 2018.3, we added a performance profiler to Rider. As we try to deliver new features as quickly as possible, the integrated profiler had some limitations: it only supported the profiling of .NET Framework and .NET Core applications on Windows. Now, it's time to fill the gap. In Rider 2019.1, the profiler gets support for Mono and Mono Unity - and not just on Windows but on macOS and Linux as well. Let's look at what it can do for you. DOWNLOAD Rider 2019.1 EAP (more…)

This year we’ve focused on two areas to enhance CLion. The first is better C++ language support and general IDE performance improvements. As a result, we’ve added a clangd-based experimental complementary language engine, and a massive amount of work was done which, although invisible at first glance, has helped eliminate dozens of UI freezes in the editor. The second area is the endless world of remote configurations. Starting with Windows Subsystem for Linux (WSL), by the end of the year it has evolved into full remote development support. Our efforts in both of these areas have culmin

Hi, The new CLion 2018.3 EAP (build 183.3647.14) is now available for download! As usual, a patch-update will be available shortly for those using the previous EAP build, and you can also use Toolbox app or snap packages (in the case of Ubuntu) to get this build. No license is required and the build is free to use, but it will expire within 30 days of the build date. Download CLion 2018.3 EAP CPU Profiler Starting from this EAP, CLion comes with the CPU Profiler integration on Linux and macOS. With Perf on Linux and DTrace on macOS you can now analyze the performance of your applica

In previous posts of our series about ReSharper performance, we've looked at a number of high-level, architectural improvements JetBrains is making in terms of performance. We also discussed software tends to accumulate smaller, local performance problems over time. In this post, we are going to highlight noticeable changes we've made in ReSharper 2018.1 and 2018.1.1 to improve performance for many scenarios. In this series: Introducing the ReSharper performance series Taking ReSharper out of process Component composition, just-in-time-compilation, the UI thread Performance imp

In the previous post of our ReSharper performance series, we have seen that it makes a lot of sense to explore running it as a separate process. This brings many benefits: both Visual Studio and ReSharper would run in their own process, have their own thread pool, and their own memory space. By itself, this is not the silver bullet that will fix performance, however. It is a big part, but there are additional areas that can be improved. In this post, we will look at improving startup of Visual Studio and ReSharper. In this series: Introducing the ReSharper performance series Taking

In the previous post of our ReSharper performance series, we looked at Visual Studio and ReSharper complexity and history, and determined that one of the reasons for degraded performance lies in Visual Studio being a 32-bit process. In this post, we will look at what can be done to overcome that limitation. In this series: Introducing the ReSharper performance series Taking ReSharper out of process Component composition, just-in-time-compilation, the UI thread Performance improvements in ReSharper 2018.1 and 2018.1.1 Let's dive in! Roslyn and ReSharper We've looked at the 32-

With every ReSharper update, we get questions around performance. Some users notice a slightly slower solution load, others see a minor indexing lag, and others get bugged by a yellow notification bar stating "Extension 'JetBrains ReSharper Ultimate' likely caused 9 seconds of unresponsiveness. Disabling it may improve your experience." - and yes, we have seen higher values there, too. We hear you. We use ReSharper to develop ReSharper. It may not always be visible, but we are working hard on improving ReSharper performance. And because those changes aren't always visible, we are starting a

During the past few weeks, the Rider 2018.1 EAP builds came with a number of new debugger features, and today's build is no different. Rider 2018.1 EAP adds another improvement: a Memory View that lets us explore the managed heap while debugging, allowing us to look into the memory space that is used by our application! When the debugger hits a breakpoint, we can open the memory view in a separate tab. After clicking the grid, Rider shows us the total number of objects in the heap grouped by their full type name, the number of objects, and bytes consumed. (more…)