If APMEvents is backed by vtproto's pool then timestamppb comes out as one of the most allocation heavy object. This was fixed in apm-aggregation by using uint64 to encode timestamps. If uint64 suits all our needs, we should consider promoting that package to apm-data: https://github.com/elastic/apm-aggregation/tree/main/aggregators/internal/timestamppb
If
APMEventsis backed by vtproto's pool thentimestamppbcomes out as one of the most allocation heavy object. This was fixed inapm-aggregationby usinguint64to encode timestamps. Ifuint64suits all our needs, we should consider promoting that package toapm-data: https://github.com/elastic/apm-aggregation/tree/main/aggregators/internal/timestamppb