Influx heavily CPU-bound during performance test

Hello,

I’ve been running some initial performance tests of influx running on an 8-core machine with NVME drives (NVME = very high performance SSD drives). The test was a write-only test writing 20 series in batches of 100 points, each point with ~10 integer fields). I compared this against running using EBS (elastic block store). I was expecting influx on NVME to completely blow away influx on EBS. But I only saw a <20% improvement. It looked like influx was heavily CPU bound (all 8 cores completely pegged by influx). So I used perf to get stack-samples and generate a flame graph: perf-first2.svg - Google Drive (download and open in chrome).

Is the performance profile shown by the flame graph expected?

I tried to upload the svg file, but I got a message saying “Sorry, new users cannot upload attachments”. Hence the link to google drive. It’s a .svg file that you can open in any browser.