Hello QuickSight Experts,
Wanted to get an understanding or information, if there’s any hard limit on QuickSight SPICE capacity for a given account. I have already gone through one of the
existing thread and understand that the hard limit is there for a given dataset. However, my question is specifically if there’s any hard limit at a QuickSight account level or we can purchase additional SPICE capacity and stretch the limit as large as possible for a given account as per our need.
Looking forward to your response to get a better understanding. Thank you!
February 8, 2023, 5:30pm
I haven’t ran into any limit and we have processed a lot of data.
My guess is no… but I do not have an exact answer.
February 8, 2023, 7:49pm
There is a 1TB limit per account per region
Isn’t the 1TB limit per dataset and not per account? Our account has over 3TB in SPICE capacity without any issues.
1 TB is only the soft limit per QuickSight account. There no known hard limits practically, It can be increased to desired capacity, on request.
This file has been truncated.
# Managing SPICE Capacity<a name="managing-spice-capacity"></a>
You can use the admin page to see how much [SPICE](welcome.md#spice) capacity you have overall, and how much of that you are using\. SPICE capacity is allocated by AWS Region, so the information displayed is for the currently selected AWS Region\.
SPICE stores your data until you choose to delete it\. You can improve performance by importing the data into SPICE instead of using a direct query to the database\. All nondatabase data sets must use SPICE\.
SPICE capacity is pooled across users for the Amazon QuickSight account\. All of your default SPICE capacity is allocated to your home AWS Region\. The other AWS Regions have no SPICE capacity unless you choose to purchase some\.
To free up SPICE capacity, delete unused data sets from SPICE\. For more information about deleting a data set, see [Deleting a Data Set](delete-a-data-set.md)\.
You can purchase additional SPICE capacity if you want to, up to a limit of 1 TB total capacity per QuickSight account\. If you need an exception to this limit, follow the instructions at [AWS Service Limits](https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) to submit a limit increase request\. You can also release purchased SPICE capacity that you aren't using\. Purchasing or releasing SPICE capacity only affects the capacity for the currently selected AWS Region\. For information about additional SPICE pricing, see [Amazon QuickSight](https://quicksight.aws.amazon.com/)\.
## Capacity Planning for SPICE<a name="capacity-planning-for-spice"></a>
The amount of SPICE capacity a data set uses isn't the same as the size of its source file or table\. The logical size computation occurs after all the data type transformations and calculated columns you define during data preparation\. These fields are materialized in SPICE in a way that enhances query performance\. Any changes you make in an analysis have no effect on the logical size of the data in SPICE\. Only changes that are saved in the data set apply to SPICE capacity\.
In capacity planning for SPICE, consider what data types will be defined in the data set\. For example, the file you want to import may contain all strings \(text\)\. But in order for these to be used in a meaningful way in an analysis, you prepare the data by changing the data types to their proper form\. For example, fields containing prices are changed from strings to decimals, and fields containing dates are changed from strings to dates\. If you create a calculation to make the conversion, you can remove the original field from the data set and substitute the formatted calculated field\. In that case, you don't need to include the size of the original field in your capacity planning\. Only included fields are stored in SPICE\.
Geospatial data types use metadata to interpret the physical data type\. Latitutde and longitude are numeric\. All other geospatial categories are strings\.