163-java-profiling-refactor

Java profiling refactoring analyzes profiling data to identify CPU hotspots, memory leaks, and threading bottlenecks, then implements targeted code changes to optimize application performance. You need to provide profiling analysis documents for the Skill to process.

The best way to optimize Java performance is through targeted refactoring based on profiling data. This approach addresses specific CPU, memory, and threading bottlenecks directly, requiring manual code changes and verifying all tests pass to maintain build integrity.

Yes, you need to provide profiling documents. The refactoring process analyzes data from designated documents like 'docs/profiling-problem-analysis-YYYYMMDD.md' and 'docs/profiling-solutions-YYYYMMDD.md' to identify and implement performance optimizations.

Profiling-driven Java refactoring ensures test verification by running all tests after implementing code changes. This maintains build integrity and confirms that performance optimizations addressing bottlenecks do not break existing application functionality.

Yes, you can use this refactoring approach to fix threading issues and memory leaks. It analyzes profiling data to identify these specific performance bottlenecks and implements targeted code changes to resolve them within your Java applications.

The main limitation is that Java performance refactoring requires manual code changes. After implementing these changes to address profiling bottlenecks, you must verify all tests pass to maintain build integrity, which requires available and comprehensive test coverage.