4 ms·
To get a relevant recommendation, you'll have to describe two things at least - data and queries. How is the data generated? What is stored in the data? What ar
by virtuabhi 12y ago
To get a relevant recommendation, you'll have to describe two things at least - data and queries. How is the data generated? What is stored in the data? What are the queries you plan to run?
- BWStearns 12y agoThe data is going to be sensor readings. Just numeric readouts over time. There will probably be about 8-16 physical sensor points per person per reading. I'll want to retrieve slices of time rather than individual records and likely produce some averages/basic algebra over those slices in order to produce more meaningful data for the rest of the system which is pretty vanilla in terms of data requirements.
- imperialWicket 12y agoI made a data star supporting weather/water sensor data in postgresql that heavily relied on table partitions for handling performance [1]. We had it on pretty weak machines, replicated with bucardo, and never had any issues. It worked well to several million records/month (not sure where it is now). [1] https://github.com/imperialwicket/postgresql-time-series-table-partitions https://github.com/imperialwicket/postgresql-time-series-tab...