jeremy-allen/claude-skills/optimizing-r

Optimizing R

This skill covers profiling, benchmarking, parallelization, and performance best practices for R.

Core Principle

Profile before optimizing - Use profvis and bench to identify real bottlenecks. Write readable code first, optimize only when necessary.

Profiling Tools Decision Matrix

Performance Workflow

1. Profile first - Find the actual bottlenecks
2. Focus on the slowest parts - 80/20 rule
3. Benchmark alternatives - For hot spots only
4. Consider tool trade-offs - Based on bottleneck type

See profiling-workflow.md for the complete workflow.

When Each Tool Helps vs Hurts

Parallel Processing (in_parallel())

Helps when:

• CPU-intensive computations
• Embarrassingly parallel problems
• Large datasets with independent operations
• I/O bound operations (file reading, API calls)

Hurts when:

• Simple, fast operations (overhead > benefit)
• Memory-intensive operations (may cause thrashing)
• Operations requiring shared state
• Small datasets

See parallel-examples.md for decision points.

Data Backend Selection

See backend-selection.md for guidance.

Profiling Best Practices

1. Profile realistic data sizes - Not toy examples
2. Profile multiple runs - For stability
3. Check memory usage too - Not just time
4. Profile realistic usage patterns - Not isolated calls

See profiling-best-practices.md for examples.

Performance Anti-Patterns to Avoid

• Don't optimize without measuring - Profile first
• Don't over-engineer - Complex optimizations for 1% gains
• Don't assume - "for loops are always slow" is a myth
• Don't ignore readability costs - Readable code with targeted optimizations

See performance-anti-patterns.md for examples.

Modern purrr Patterns

Data Frame Binding (purrr 1.0+)

Side Effects with walk()

Use walk() and walk2() for side effects (file writing, plotting).

Parallel Processing (purrr 1.1.0+)

Use in_parallel() with mirai for scaling across cores.

See purrr-patterns.md for all patterns.

Backend Tools for Performance

When speed is critical, consider:

• vctrs - Type-stable vector operations
• rlang - Metaprogramming
• data.table - Large data operations

Profile to identify whether these tools will help your specific bottleneck.

source: Sarah Johnson's gist https://gist.github.com/sj-io/3828d64d0969f2a0f05297e59e6c15ad