Optimize writes to InfluxDB
Use these tips to optimize performance and system overhead when writing data to InfluxDB.
The following tools write to InfluxDB and employ write optimizations by default:
Write data in batches to minimize network overhead when writing data to InfluxDB.
The optimal batch size is 5000 lines of line protocol.
Sort tags by key
Before writing data points to InfluxDB, sort tags by key in lexicographic order.
Verify sort results match results from the Go
# Line protocol example with unsorted tags measurement,tagC=therefore,tagE=am,tagA=i,tagD=i,tagB=think fieldKey=fieldValue 1562020262 # Optimized line protocol example with tags sorted by key measurement,tagA=i,tagB=think,tagC=therefore,tagD=i,tagE=am fieldKey=fieldValue 1562020262
Use the coarsest time precision possible
By default, InfluxDB writes data in nanosecond precision. However if your data isn’t collected in nanoseconds, there is no need to write at that precision. For better performance, use the coarsest precision possible for timestamps.
Specify timestamp precision when writing to InfluxDB.
Synchronize hosts with NTP
Use the Network Time Protocol (NTP) to synchronize time between hosts. If a timestamp isn’t included in line protocol, InfluxDB uses its host’s local time (in UTC) to assign timestamps to each point. If a host’s clocks isn’t synchronized with NTP, timestamps may be inaccurate.
Write multiple data points in one request
To write multiple lines in one request, each line of line protocol must be delimited by a new line (
Bug Reports and Feedback
Thank you for being willing to help test InfluxDB v2.0 alpha! Feedback and bug reports are welcome and encouraged both for InfluxDB and this documentation. Submit feedback using one of the following methods: