Best practices regarding object lifetimes (InfluxDBClient, WriteApi)

[naymore]

// tried feature request and it didn't work, I swear!

Proposal:
Line out best practices in the documentation how to efficiently write to InfluxDB using the C# SDK

Current behavior:
I'm uncertain which object to keep as a singleton and which ones to keep transient.
Currently I am holding on to my InfluxDBClient instance and create a new WriteApi instance every single time I need to write a new measurement.

Desired behavior:
Explanation how to be efficient.

[snoopiedoom]

+1 would be greatly appreciated
In our case, we're running a client for each bucket/retention policy with custom batching, delivering the client an array of line protocol strings, works for now.

[harzus]

and once you're at it, would you include also python