Op dinsdag 15 december 2015 02:16:02 UTC+1 schreef Sean Beckett: > If you have highly dynamic data, that should be stored as a field, not a tag. > That makes it impossible to use with GROUP BY clauses, however, which I > suspect is a non-starter for you.
Is there a way to guesstimate the memory requirements from the cardinality? We're looking to analyse how people flow through our building by analysing our radius logs. From these, we get a measurement approx every 30 seconds per user that couples a user (or device) to an access point. Picking a random day from the logs puts us at 7.5k access points to which some 500 users connected. That'd get us a cardinality of about 3.75M... that's not going to end well I take it then. If we broaden the sample, we're likely to approach 30k users over the lifetime of the analysis. -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" 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/3d709e55-7a67-44c8-9b35-79693e26e65c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
