InfluxDB batch writes from file - does measurement order matter?

InfluxDB 1
1

I’m new to InfluxDB and looking to parse some JSON data for inserting into InfluxDB 1.8 based database using batch files and was wondering for performance, does the order of measurements in the batch files matter?

For example at k6-benchmarking/k6-log-parsing.md at master · centminmod/k6-benchmarking · GitHub

I could parse each group of metrics as measurements individually

for http_reqs and http_req_duration measurements

http_reqs,stage=3,testname=rampingvus,scenario=ramping_vus,name=https://domain1.com,status=200,expected_response=true value=1 1665468046944
http_reqs,expected_response=true,scenario=ramping_vus,stage=3,testname=rampingvus,name=https://domain1.com,status=200 value=1 1665468053071
http_reqs,testname=rampingvus,scenario=ramping_vus,stage=3,name=https://domain1.com,status=200,expected_response=true value=1 1665468059117

http_req_duration,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.19456 1665468046944
http_req_duration,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.19281 1665468053071
http_req_duration,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.184015 1665468059117

or just parse them all together where the order of measurements would be mixed, but entries in the file would naturally already be ordered by timestamp ascending

http_req_waiting,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.145535 1665468053071
http_req_receiving,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.018073 1665468053071
http_req_failed,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0 1665468053071
http_reqs,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=1 1665468059117
http_req_duration,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.184015 1665468059117
http_req_blocked,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.000222 1665468059117
http_req_connecting,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0 1665468059117
http_req_tls_handshaking,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0 1665468059117
http_req_sending,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.029498 1665468059117
http_req_waiting,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.139135 1665468059117
http_req_receiving,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0.015382 1665468059117
http_req_failed,expected_response=true,name=https://domain1.com,scenario=ramping_vus,stage=3,status=200,testname=rampingvus value=0 1665468059117