I don't think that you can query this kind of huge TW model with current TW features ( without putting an infinite server on it ). Some solutions:
- If questions are known in advance, easily you can aggregate data while you are storing it, or in batch each day --> Actually we are doing this.
- If questions aren't known in advance, you may need to push all your model data to a Business Intelligence/Big Data tool where you can query easily huge amounts of data.
Hope it helps,
Hmmmm. Was speaking to a colleague and he mentioned that Things (assets) are already in memory (as they have to be able to respond to events etc...).Therefore, my assumption about additional memory seems to be wrong. However, there is still a concern regarding performance. We haven't yet performance tested the aggregation functions across a large number of assets.