Hosted Feature Storage size doesn't change

Question

Hello everyone,

we are implementing AGOL in our company and would like to understand a (maybe not) strange behaviour regarding the size of the hosted feature storage.

I've noticed that the Feature Storage Size of my layers never changes, even when I add or remove items.

For example :

* 350Mb layers using the same storage even if I removed 450k items
* No changes in the hosted feature size while I emptied 2 of the 4 layers

I ran multiple report to see if the error was just on the details page but I have the same number.

Also those layers are not activated for editing, offline etc.

Is it a normal behaviour, me doing something wrong or just a known bug ?

It is kind of important regarding credits consumption tracking and all those stuff

Thanks in advance for you help and best regards,

D_McRitchie · Answer

Hey Gilles,

It might be worth raising a support case with your software provider. One thing I would flag is check if you have editor and change tracking enabled?

The backend change tracking tables can grow in size rapidly, particularly if we have any automated processes in data. I have seen Feature Layers with no active attributes have a size larger than 2GB just due to the Change tracking tables.

I would also confirm that we have waited several hours after making any changes before reviewing the reported layer size as ArcGIS Online will not update this immediately.

Hope that helps,

David

GillesTichy · Answer

Hello,

So I slept on it for the weekend and this morning everything seems now up to date.

I run an automatic report every sunday and it shows size was still wrong yesterday 🙄

I'll run some tests to check if it was a bug and try your tip in case it is still happening.

Thanks for your reply !

PeterKnoop · Answer

I've had a similar experience with size and credit charges not going down as expected when features are deleted. See this thread about needing to use Compress and then adding a dummy feature to actually free up the storage: https://community.esri.com/t5/arcgis-online-questions/reduction-of-space-and-credit-consumption/m-p/1392911/highlight/true#M57968

You might give the Compress and edit route a try on your feature layer to see if that reconciles things with what your are expecting.