Jakub Bednář

Any progress?

Hi @fcoetzee, As you mentioned the `datetime` has a precision to microseconds and also almost all time libraries are without supports of nanoseconds: - [pendelum](https://github.com/sdispater/pendulum/) - [udatetime](https://github.com/freach/udatetime) - [isodate](https://github.com/gweis/isodate/) -...

Hi @lennartklfhs, your question is related to v2 client - [influxdb-client-python](https://github.com/influxdata/influxdb-python/issues/762). The default configuration of `write_api` uses underlaying queue to insert batches into InfluxDB. You have to call `write_api.close()` to...

Hi All, the [influxdb-client-python](https://github.com/influxdata/influxdb-client-python) supports `async/await`. For more info see: - https://influxdb-client.readthedocs.io/en/stable/usage.html#how-to-use-asyncio - https://influxdb-client.readthedocs.io/en/stable/api_async.html Regards

Hi @georgescumihai, did you find solutions? Regards

Hi @2mik, thanks for using our client. Is this something you might be willing to help with? Regards

Hi @CordisSSegers, thanks for using our client. Can you share a little bit more about your code that ingest data into InfluxDB? Does the InfluxDB sufficient hardware resources? The problem...

Just after a quick look, I think you have everything set up right. For importing large amounts of data it would be better to set `FlushInterval` to a large value...

Hi @broadside74, the `writeApi` should be cached in a field and disposed when your application end. For your use cases (~200 points per sec) you can use `WriteApiAsync` and write...

@broadside74 For your use case will be better to use `InfluxDbClient.GetWriteApiAsync()` and use `WriteMeasurementsAsync(TM[])`. The `WriteMeasurementAsync(TM)` could be to stressful for the server