- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Athena allocates resources dynamically based on overall service load and query volume. Queries go through a queuing process before being assigned resources.
The queuing system aims to distribute resources efficiently across all customers. It's possible your workload was not large enough to fully utilize the reserved capacity.
Factors like query complexity, data size and distribution of requests over time can impact how much of the reserved capacity gets utilized at a given time.
Utilization levels tend to average out over longer periods as workloads and queues fluctuate. Running the workload repeatedly may give a more accurate picture of long term utilization.
You can check Athena documentation or contact support for guidance on sizing capacity reservations based on expected query patterns and SLAs. Over-provisioning is minimized through Athena's flexible resource allocation.
The reservation ensures your important workload always has priority access to resources, even during peak usage. But full utilization at every moment is not guaranteed.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Hi there,
Is there any way to look at the logs that explains the queuing mechanism?
Not sure I agree with this. I ran the standard queries on my serverless workgroup and noticed a pretty big difference.
My gripe with this is, if the workload wasn't big enough the queries on provisioned capacity should have finished at the same time as serverless or even faster.