will an additional, rarely changing tag have a relevant "cost"?

Viewed 5

In a InfluxDB (Cloud) I store measurements of a many weather sensors.

So, each InfluxDB data point looks like this:

weather,deviceId=1234 temperature=21.3,humidity=66 1559260800000000000

To the existing single deviceId tag I'd like to add a second tag position, resulting in points such as...

weather,deviceId=1234,position=243 temperature=21.3,humidity=66 1559260800000000000

For a given deviceId the position would change very rarely, but it can happen.

When querying a sensor data, the deviceId and position would be filtered always together.

Will this additional tag have an relevant increase on the billed storage (GB-hr) or negatively affect performance or is InfluxDB able to optimize/compress this additional tag?

Some more context: Some sensors might be reused and placed to a different location. It would not make much sense to analyze data of a single sensor at different positions, hence filter data always like "sensor 1234 at position 243". As this is adding a fifth value to a otherwise relatively small data point, I'm worried that this might "cost" too much.

0 Answers
Related