Break down of SPICE capacity chart

hi,

I’m trying to make sense of the following SPICE capacity chart. We have 299GB of Free Bundle Capacity plus 50GB of purchased. I also have a SPICE dataset of 900GB+

So what are the following metrics:

  1. What is this 1.05TB, is it the hard limit for each account?
  2. What are those 267.67, 535.35, 803.02 etc marks?
  3. For the 1.05TB-350GB Over Capacity, does it mean it’s the capacity I can use but I haven’t purchased it yet.

Thanks,

Hi @Leon,

1.05TB isn’t the hard limit for your account. It’s showing that you’re using using 1.05TB. Normally your refreshes should fail if you don’t have enough capacity, so I don’t know how you were able to go over capacity by this much.

The 4 marks seem to be representing 25%, 50%, 75% and 100% of your current usage.

1 Like

@David_Wong

So it would fail if it goes over 350GB?

I still don’t understand this Over capacity thing, does it mean it’s being used as part of the capacity or it needs this amount of capacity for the dataset to ingest data. I don’t remember purchasing extra capacity, 350GB is all we have.

Thanks,

Over capacity means you’re using more SPICE than what you bought + what you’re getting for free. The next time you refresh a dataset, the refresh will fail. If you want to prevent your refreshes from failing, you have to buy more SPICE capacity or delete datasets until the red portion of that bar is gone.

Hi @Leon thanks for the question, let me try to clarify the behavior.
When an ingestion is requested, QS cannot accurately estimate the size of the dataset, therefore, the logic is to start ingestion as long as there are >0 capacity left. We would only know the size when ingestion is finished, which might already have been several hours. With that logic, it is possible that the final used capacity exceeds the purchase capacity. For user friendliness, QS still allows that as an exception path. But all the following ingestion will be failing since there are no purchased capacity left.
Please note, if this (over capacity) happens, we WILL charge for the actual usage, rather than the purchased capacity. If users want to enforce the limit, the admin will have to delete the dataset. Or the admin needs to purchase more SPICE capacity to avoid further ingestion failure.
Please let me know if further clarification needed. Thanks!