Performance and Benchmarks
This page provides performance expectations and optimization guidelines for AsteroidThermoPhysicalModels.jl.
Expected Performance
The following benchmarks were performed on Apple M4 (macOS, single-threaded):
Single Asteroid (Ryugu)
- Shape complexity: 49,152 faces
- 1 rotation (72 time steps): ~5.2 seconds
- 20 rotations (1,440 time steps): ~101 seconds (1.7 minutes)
- Memory usage: 152 KiB (20 rotations), 5.8 KiB (1 rotation)
- Allocations: 20 (20 rotations), 16 (1 rotation)
- With shadows and self-heating enabled
Binary System (Didymos-Dimorphos)
- Primary: 1,996 faces, Secondary: 3,072 faces
- 1 rotation (72 time steps): ~4.6 seconds
- 20 rotations (1,440 time steps): ~92 seconds (1.5 minutes)
- Memory usage: 53.65 MiB (20 rotations), 1.70 MiB (1 rotation)
- Allocations: 594,141 (20 rotations), 3,409 (1 rotation)
- With mutual shadowing and heating enabled
Component Performance (per time step)
- Shadow calculations: ~0.38 seconds (27.3s for 72 steps)
- Self-heating: ~0.41 seconds (29.4s for 72 steps)
- Temperature update: ~0.40 seconds (28.5s for 72 steps)
Note: Component benchmarks show total time for 72 calls in isolation
Note: Performance may vary depending on CPU architecture. Intel/AMD processors may show different characteristics.
Performance Considerations
Computational Complexity
The main computational bottlenecks are:
Shadow calculations: O(N²) where N is the number of faces
- Dominates computation time for large shape models
- Can be disabled with
SELF_SHADOWING = false
for faster computation
Self-heating: O(N×M) where M is the average number of visible faces
- Uses precomputed visibility graph
- Can be disabled with
SELF_HEATING = false
Temperature solver: O(N×D) where D is the number of depth layers
- Typically not a bottleneck unless using many depth layers
Memory Usage
Memory scales approximately as:
- Shape model: O(N)
- Temperature array: O(N×D)
- Visibility graph: O(N×M) where M is average visible faces per face
For Ryugu (49k faces, 41 depth layers):
- Expected memory usage: 2-3 GB
- Peak during visibility computation: 4-5 GB
Optimization Tips
1. Disable Features for Faster Computation
# Fastest configuration (no shadows or self-heating)
stpm = SingleAsteroidTPM(shape, thermo_params;
SELF_SHADOWING = false,
SELF_HEATING = false
)
2. Reduce Shape Complexity
For preliminary calculations, use a simplified shape model.
3. Adjust Time Resolution
Larger time steps can be used for initial calculations:
# Use fewer steps per rotation
n_step_in_cycle = 36 # Instead of 72
4. Parallel Execution
The package supports multi-threading for some operations:
# Start Julia with multiple threads
# $ julia -t 8
# The visibility graph computation will use available threads
Version Performance History
v0.0.8-DEV (Current)
- Added comprehensive benchmark suite
- Performance tracking infrastructure
- Migrated to AsteroidShapeModels.jl v0.4.0 with batch illumination processing
- Improved visibility graph API
- Performance: Ryugu 20 rotations in ~101s, Didymos in ~92s
- Memory: Ryugu uses 152 KiB, but Didymos binary system shows higher allocation count (594k allocations)
- Latest benchmark: 2025-07-09 (Apple M4)
v0.0.7
- Memory optimizations in flux calculations
- Basic shadow and self-heating calculations
Earlier versions
- Initial implementation
- Basic thermophysical modeling
Benchmarking Your Configuration
To benchmark your specific use case:
using BenchmarkTools
using AsteroidThermoPhysicalModels
# Your setup
stpm = # ... your model
ephem = # ... your ephemerides
# Benchmark
@benchmark run_TPM!($stpm, $ephem, Float64[], Int[]; show_progress=false)
For detailed benchmarking, see the benchmark/
directory in the source repository.