Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    So you are suggesting that the data be indexed by timestamp and partitioned by month. What value does the partitioning across multiple databases provide here? I would expect the data is already indexed by timestamp. Queries over large time spans will still be slow. Or are you suggesting a MapReduce style approach where different months can be searched in parallel? Commented Nov 19, 2017 at 9:44
  • Queries get slower as the db grows and there will be a maximum size to a single database, either because of limits imposed by the db itself or by volume size restrictions. Commented Nov 19, 2017 at 10:16