Open Subsegment opened 7 months ago
Perhaps you can use sampling tool (such as jprofile or arthas) to find out what function takes so much cpu when testing cnosdb and influxdb.
You can use the testWithDefaultPath
pattern directly, where verificationWriteMode
checks the correctness of all data written, which is not needed for normal performance tests and can be CPU-expensive
Description
After I implemented Iot-benchmark support for CnosDB, I found that the iot-benmark itself had a very high cpu usage during testing.But in fact, the concurrency is not much, CnosDB itself has a relatively low CPU usage, is this my implementation problem?
I also tested Influxdb and found a similar one for iot-benchmark-influxdb
But when I tested iotdb, there was no problem with high cpu usage. Why?
Config
here is my config