Timestream query performance very slow, seemingly with the switch to TCU based pricing

As a follow up, our query cost has now skyrocketed since switching to TCU based pricing, alongside a massive decrease in performance. Kind of a joke, really, and we may need to find an alternative to Timestream at this point. Really quite a bummer AWS.

Timestream Compute Unit (TCU) is a different mechanism for metering. The underlying infrastructure used for either bytes-scanned or TCUs based metering is the same, implying that there shouldn't be impact on query performance. If you are noticing a performance impact, can you create a support ticket for the service to investigate this further.