Public signup for this instance is disabled. Go to our Self serve sign up page to request an account.
I've been profiling a complex streams job, and found two major hotspots when writing metrics, which take up about 60% of the CPU time of the job. A PR is attached.
Sampling on throughput / latency metrics recording in Streams
Fetcher spending unnecessary time during metrics recording
GitHub Pull Request #1447
GitHub Pull Request #1490
GitHub Pull Request #1530