This reverts commit 5c9baf7a567f9bac8cd1cd00c8801c06d34eb353.
It appears that the introduction of profiling is interfering with benchmarks, causing "queue is full" errors. We could increase queue.mem.events, but there will still be interference. I think a better approach would be to configure the apm-server under load to send its events/metrics/profiles to a separate apm-server, to minimise interference.
This reverts commit 5c9baf7a567f9bac8cd1cd00c8801c06d34eb353.
It appears that the introduction of profiling is interfering with benchmarks, causing "queue is full" errors. We could increase
queue.mem.events, but there will still be interference. I think a better approach would be to configure the apm-server under load to send its events/metrics/profiles to a separate apm-server, to minimise interference.