ptrace performance

[XiaoWeiKIN]

I was converting some of my internal traces data to otlp data, and I needed to consume these json type data from kafka and serialize it to ptraces, so I developed a custom encoding extension, but I found that ptraces AppendEmpty was constantly creating objects, So I wanted to use sync.pool optimization, but found that there was no API to use, and the properties were all packaged in-house. Do you have any plans?

[dmathieu]

If this data is generated outside the collector, you should probably be using the protobuf directly rather than pdata.
Doing so will still let you ingest into the collector (pdata is an abstraction on top of protobuf), and will let you use a pool as you need.

https://github.com/open-telemetry/opentelemetry-proto-go

[XiaoWeiKIN]

thanks @dmathieu , but traces consumer requires ptrace.Traces, how should I create ptrace.Traces through https://github.com/open-telemetry/opentelemetry-proto-go without related API

// Traces is an interface that receives ptrace.Traces, processes it
// as needed, and sends it to the next processing node if any or to the destination.
type Traces interface {
	internal.BaseConsumer
	// ConsumeTraces receives ptrace.Traces for consumption.
	ConsumeTraces(ctx context.Context, td ptrace.Traces) error
}