Select to view content in your preferred language

GP service performance -- what does GPServerSync.Save do and why it takes so long

641
1
03-15-2022 07:47 AM
JianLiu5
New Contributor

We are looking to improve a GP service response time. The script execution itself has been greatly improved, however, we've noticed this server process "GPServerSync.Save" takes a long time for orders with large return set. For example, below shows some sample log: 

 

TypeMessageTimeCodeTime ElapsedProcessThreadMethod Name
VERBOSEGPServerSync.Deactivate2022-03-14T15:03:07200250.01937138808668GPServerSync.Deactivate
FINEREST request successfully processed. Response size is 12153301 characters.2022-03-14T15:03:071000049.91373138808668tasks/TPO Analysis/execute
VERBOSESave job jf0e510b0bc304bcc8d89ae0627dd4b01 message type REST message size 1772042022-03-14T15:03:07200244.73296138808668GPServerSync.Save.TPO Analysis
VERBOSEExecute job jf0e510b0bc304bcc8d89ae0627dd4b012022-03-14T15:03:02200224.90342138808668GPServerSync.Execute.TPO Analysis

 

Note the script execution itself takes 4.9 seconds, which is pretty satisfactory. However, the ArcGIS Server process "GPServerSync.Save" takes 4.7 seconds. That is a HUGE overhead. What does it do and why it takes this long?? (I've noticed this step doesn't always take that long, the time it takes seems to be proportional to the message size, which I assume is proportional to the size of the return set)

 

Any insiders, please offer some insights. Thank you. 

1 Reply
Ranga_Tolapi
Frequent Contributor

Hi @JianLiu5

Can you please help to share your findings on this. Thank you. 

0 Kudos