nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hosted Feature Service Too Big?

PeterTimmers

Why would a hosted point feature layer with less than 100 points and no attachments take 9GB?

We do edit the feature layer a lot.

Encontre mais publicações marcadas com

Accepted answers

All comments

NickShannon2

@rachelg_esri wrote:
If you temporarily disable the syncing, then re-enable it, you effectively clear out those tables.

Hi Rachel,

Thanks for the advice — I now understand why my empty FHS were so large in size.

WRT disabling the sync — this is a good idea, but the trouble is if the FHS has been taken offline in FieldMaps/Collector, it won't sync again even if you've re-enabled sync on the FHS. There is a warning: Unable to synchronise replica (because it's been removed!).

I've been investigating a method to update a very large, sync-enabled, FHS. While it is possible to do so using the ArcGIS Python API (delete rows & append), I'm always going to have the problem of every growing replicas.

So, going back to the drawing board, I think creating a MMPK or a VTPK is the way to go.

Prepare maps for download—ArcGIS Field Maps | Documentation

disable sync warning message

Sync failed message in Windows Collector

PeterTimmers

Hi Rachel,

It was the syncing. Decided to turn it off permanently. Was not a definite requirement to go offline.

Went from 9GB to 0.4MB 🙂

Thanks

rachelg_esri

Hello Peter!

Syncing is the one I worry the most about the list above, given your results. Sync tables are not directly visible in the hosted feature service, and are back-end tables. Whenever a device with the data goes offline (Collector offline usage, for example), the back end tables are keeping track of a lot of information about what rows are being used by what users. Over time, those sync tables can get pretty big.

If you temporarily disable the syncing, then re-enable it, you effectively clear out those tables. I'd choose a time when you know no one will be accessing/using the feature service, then flip that toggle (make sure everyone's checked back in first!). Then see if the size drops.

Here's a bit of information on Syncing at the following link (scroll to the "Allow offline editing or collaboration" section):

ArcGIS Online: Manage Hosted Feature Layers

Let us know if that helps?

Thank you!

Best regards,

Rachel

Esri Support Services

PeterTimmers

- Do you have attachments enabled and in use on your hosted feature service?
  - Not enabled
- Do you have any of the following settings turned on in your feature layer settings?
  - Optimize Layer Drawing - not enabled
  - Enable editing - is enabled
  - Keep track of created and updated features - is enabled
  - Keep track of who created and last updated features - not enabled
  - Enable Sync (disconnected editing with synchronization) - is enabled

So one of those options affect size? Is there archiving somehow?

rachelg_esri

Hello Peter!

There could be a few things at play here:

Do you have attachments enabled and in use on your hosted feature service?
Do you have any of the following settings turned on in your feature layer settings?
- Optimize Layer Drawing
- Enable editing
- Keep track of created and updated features
- Keep track of who created and last updated features
- Enable Sync (disconnected editing with synchronization)

Let me know if you need help finding any of this.

Thanks!

Best regards,

Rachel

Esri Support Services

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.