Fully featured low overhead profiler for Java EE and Java SE platforms.
Monitoring and profiling solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Solving performance problems

What performance problems may arise?

  • Application algorithms are usually not optimal, which leads to performance bottlenecks.
  • For memory-related issues see below.

Why memory-related issues can cause performance problems?

Memory-related issues can affect an application's execution speed and stability:

  • When CLR cannot allocate an object (because it is out of memory, and no more memory can be freed by the garbage collector), OutOfMemoryError is thrown, which can cause an application crash or further unstable operation.
  • An application that uses a lot of memory reduces available physical memory for itself and other programs, and thus forces the operating system to swap memory pages to and from the disk more frequently. This leads to serious overall system performance degradation.
  • CLR spends more time to perform garbage collection when more objects exist and more temporary objects are created.

Read more about memory-related problems: