On Monday, July 11, 2016 at 7:35:58 PM UTC+2, Sean Beckett wrote: > > Yes, you'd have a series for each unique trip ID. The car would be > identified by the "id" tag, presumably. > > You probably want to use a tag for "trip" so that you can group by trip ID > and performantly query by trip ID. > > However, if you anticipate millions of trip IDs, it would be better to > store it as a field so that your series cardinality > <https://docs.influxdata.com/influxdb/v0.13/concepts/glossary/#series-cardinality> > > doesn't rise too high and require lots of RAM > <https://docs.influxdata.com/influxdb/v0.13/guides/hardware_sizing/#when-do-i-need-more-ram> > . > > Well, not millions. The first year we had an average of 350 trips over 3 cars, so that should be OK. Over the next few years, we anticipate about 20 car ids, and some 50k trips each (with two cars having the same trip ID would be very unlikely, although not impossible), so if I read that latter page right, we should be OK until the end of the project as long as we keep adding RAM. What's the Y axis on that latter chart?
Is there a way to bulk-add tags to a set of existing measurements? We also want to add refuel points to our time series, but those can only be calculated later. -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/6c9b9776-6b7a-45b0-8d34-902ccd30f3ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
