# Performance Myths and Continuous Profiling

DevFeed: [Performance Myths and Continuous Profiling](<https://devfeed.tech/articles/performance-myths-and-continuous-profiling-25640.md>)

Original publisher: [Read original article](<https://richardstartin.github.io/posts/perf-myths-and-continuous-profiling>)

Author: Richard Startin's Blog

Published: 2021-12-27T00:00:00Z

Content type: opinion

Language: en

Sources: [Richard Startin's Blog](<https://devfeed.tech/sources/richard-startin-s-blog.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [coding](<https://devfeed.tech/topics/coding.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [compiler](<https://devfeed.tech/tags/compiler.md>), [java](<https://devfeed.tech/tags/java.md>), [performance](<https://devfeed.tech/tags/performance.md>), [profiling](<https://devfeed.tech/tags/profiling.md>)

## AI overview

The article examines performance myths affecting Java programming, distinguishing claims that were never true from practices that were once useful. It uses examples such as increment operators and string concatenation before discussing continuous profiling as a way to evaluate performance issues.

## Source excerpt

My last post was about five very simple things you can do to avoid Java programs from being slower than they need to be. The reception to this post was mixed. Some readers agreed that the problems mentioned in the post were indeed very common, while others suggested more common inefficient patterns to avoid. For example, I could have suggested to precompile regular expressions, or not to program by exception, or to avoid String.format, but I felt this was all well covered already. The aim of the post was to help Java programmers to program defensively for efficiency - just as many do for correctness - by giving an idea of what some common things cost. However, several readers dismissed the content of the post as premature optimisation.