SPICE capacity over consumption

Question & Answer
, ,
1

Hi,

I’ve had problems with Quicksight calculating SPICE capacity consumption on multiple accounts. Basically what happends is that All of a sudden capacity is filled and it is not reduced by reducing the size of datasets, moving them to direct query, etc. Even after this, capacity suddenly spikes for no reason, jumping from 9 to 19 to 25GB in 24hrs.

The first time it happened aws support was contacted and the case was solved eventually, however this as happened on 3 accounts (different businesses). Some of these don’t have a support plan, and getting one is more expensive than what they are willing. Unfortunately this has left me with few options. What can I do? At this point it is not worth it to continue working with Quicksight in projects if apparently common problems like this force you to continue spending more and more on capacity.

This last time the problem is even worse, Quicksight has stopped showing us the size of datasets, it just shows 0 bytes. This is even worse because previously we could at least find the size of the datasets and verify that Quicksight said we were using more capacity than we were, but now we don’t even know how much capacity we’re supposed to be using.

Is there a way to resolve this issued without having to keep spending a minimum of $29+ a month to get support?

2

Hey @jmgca ,

this sound unfortunate - i haven’t had any problems with spice capacity but maybe you could provide some insights on how often and how you upload the datasets.
Also are there more people uploading data that you can’t see? You can list the datasets and show the size through the API - here is a good explanation: How can I free Spice capacity? | AWS re:Post (repost.aws)
Maybe some datasets got duplicated or other people uploaded something without your knowledge.

Hopefully this can help you. If you need any support regarding the API or have more questions feel free to ask.

BR

Robert

3

I had the same issue in the past where one of my dataset is causing sudden spike. I would advise to review all your changes in the dataset. Look at the sizes if each dataset. You could also compare the rows ingested if there is any significant increase.

4

Hi @jmgca, did this solution work for you? I am marking this reply as, “Solution,” but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community!