This is a while ago, but I'm having trouble finding other answers related to running multiple DBs.
We're also thinking of splitting our db into multiples based on our highest cardinality tag (a uuid basically). Would you mind explaining why this scheme drives up series cardinality? I'd guess the RAM requirements should probably grow, since it's now an index per DB, but since your dropping a tag that greatly increases the cardinality, my assumption was both setups should have RAM usage in the same order. -- 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/29048143-7587-4171-8789-06972d980c18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
