Portal performance with versioned data

JoeHershman

Hi,

I am seeing issues with the performance in Portal Web Maps or Apps when the referenced service uses versioned data.  I am not sure if there is a setup or configuration that I am missing.

If I add a Feature Service to a Web Map that is created from referenced data to a versioned database a few things are observed.

• The layer will often not draw completely and the "Layer did not draw completely" message is displayed
  • The occurrence of this can be changed by modifying the "Maximum Number of Records Returned by Server" setting
• The drawing is horrendously slow at times.
• During a redraw the ArcGIS Service will begin to spawn numerous instances.  I have seen it have as many as 16 running (the max at the time)
  • This is a single WebMap being redrawn which will create this number of instances.

When I use a feature classes from an enterprise database that are not versioned (e.g., archive enabled non-versioned data) or use hosted data things work much more as one would expect.  None of the items above present themselves (I still think the draw performance could be better, though).

Does anyone know why I am seeing this behavior? 

Thanks

-Joe

DerekLaw

Hi Joe,

Not sure, but perhaps this patch might work for you: Portal for ArcGIS 10.5 Large Membership Performance Patch 

EDIT: In thinking about this further, I think what you're seeing may be expected behavior. Let me explain: when you version a feature class in a geodatabase, what happens behind-the-scenes is you make 2 copies of your feature class business table (e.g., you create an 'Adds' and a 'Deletes' table) to store and track edits to the feature class. Each time you do something with the feature service - that is powered by a versioned feature class, the software will need to query and get info from all 3 tables that comprise the versioned feature class. This may be affect performance, as compared to a feature service that uses non-versioned feature class data. Does this make sense?

FYI: to learn more about versioning: Versioning 101 ArcUser technical article

I don't think the patch I mentioned previously will help with your performance issue.

Hope this helps,

dashboard.png