- Newest
- Most votes
- Most comments
Hi,
In your calculation, you assume that each of your queries will use the full 4 TCUs, but how are sure of that ?
The doc explains clearly that the number of billed TCUs depends on the complexity of your query:
https://docs.aws.amazon.com/timestream/latest/developerguide/tcu.html#maxquery-tcu
This setting specifies the maximum number of compute units the service will use
at any point in time to serve your queries. To run queries, you must set the minimum
capacity to 4 TCUs. You can set the maximum number of TCUs in multiples of 4, for example, 4, 8, 1
6, 32, and so on.
You're charged only for the compute resources you use for your workload.
For example, if you set the maximum TCUs to 128, but consistently use only 8 TCUs.
You'll be charged only for the duration during which you used the 8 TCUs. The default
MaxQueryTCU in your account is set to 200. You can adjust MaxQueryTCU from 4 to 1000,
using the AWS Management Console or UpdateAccountSettings API operation with the
AWS SDK or AWS CLI.
So, I'd suggest that you make measurements of costs on your specific queries to see if you use 4 or less TCUs per query. Then, you can compute the cost of your visits. [The rest of your computation seems ok to me]
Best,
Didier
We got a billing surprise due to TimeStream queries. The number of TCU used is apparently based on the number of queries per second. Each time you start a TCU it costs 30s. And it is in no way granular. Using the pricing calculator if you set the number of real-time queries to 17/h you get a $0 cost, but if you bump it to 18/h the cost is $1700. It will then show the same cost all the way to 25325/h but at 25326/h it doubles.
For simplicity, the pricing calculator assumes seven concurrent queries per second are served with 4 TCUs at a latency of 1 second. The pricing calculator divides the number of queries to be uniformly distributed across the given time unit (per second, minute, hours, day, month). In some cases, where queries don’t run for more than 30 seconds (including the idle period), you’re not charged for the entire minute, and the calculator doesn’t take this into consideration, so your actual totals could be much lower than displayed. https://aws.amazon.com/blogs/database/understanding-and-optimizing-amazon-timestream-compute-units-for-efficient-time-series-data-management/
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
I set my MaxQueryTCU to 4.
I can see the Admin Dashboard in Timestream itself. Every time Recources get used, it's always 4 TCUs. The graph I see should look like a graph, but it looks more like a bar diagram (spikes to 4 at times the TCUs get used).
“make measurements of costs on your specific queries” would that it were so easy! Cost is only exposed through the billing dashboard/cost explorer, not per-query.