Sample Findings
Two way aggregation
- Easier object sharing maintenance. One will know exactly when an object is shared, and which objects are its aggregates.
- Simplified DRM. Several classes whose purpose were to establish up links to the parent classes can be removed, while still maintaining the same semantic content.
- In the examined cases, the combined extra overhead incurred, in most cases, was less than 4% of the total size of the Transmittal.
GeoTIFF Application Example
- Initial execution time 11 minutes
- After profiling API improvements, reduced to 2.5 minutes
- Application re-coded to better use the API, execution 3 seconds