SPICE Refresh Times: SPICE typically handles 1M records within seconds to a couple of minutes, depending on dataset size and complexity. There is no hard time limit for SPICE refreshes, but larger datasets (10M+ records) may take longer, especially if transformations are applied.
[Update from QuickSight team - SPICE refreshes are allowed to run up to 10 hours which is more than sufficient for most customer use cases. ]
Direct Query Performance: Direct Query retrieves data in real-time but can be slower if the source system has latency or the queries are complex. It’s recommended to use Direct Query only for datasets requiring real-time data.
Performance Factors:
Dataset size: Break large datasets into smaller, focused datasets.
Complex calculations: Move calculations to the dataset or source level.
Number of visuals: Reduce visuals on a single sheet and spread them across tabs or dashboards.
Let me know if you need more help on this - I would recommend raising a support ticket to schedule a Chime call with the AWS Support team. This will allow them to review your data and provide insights into what might be happening.
Hi @Venkat.Metadata - If you are taking the data from SPICE in your visual, then it should be fast unless you have lots of calculated field, possibly you need to push them in data preparation stage so that calculation will happen first and then SPICE can be populated. It depends upon your usecase. If you can give more details on the transformation and calculation logics, then we can guide you. In parallel, as @shravya suggested, raised a ticket to AWS team and get their recommendations as well.