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:
Type | Message | Time | Code | Time Elapsed | Process | Thread | Method Name |
VERBOSE | GPServerSync.Deactivate | 2022-03-14T15:03:07 | 20025 | 0.01937 | 13880 | 8668 | GPServerSync.Deactivate |
FINE | REST request successfully processed. Response size is 12153301 characters. | 2022-03-14T15:03:07 | 100004 | 9.91373 | 13880 | 8668 | tasks/TPO Analysis/execute |
VERBOSE | Save job jf0e510b0bc304bcc8d89ae0627dd4b01 message type REST message size 177204 | 2022-03-14T15:03:07 | 20024 | 4.73296 | 13880 | 8668 | GPServerSync.Save.TPO Analysis |
VERBOSE | Execute job jf0e510b0bc304bcc8d89ae0627dd4b01 | 2022-03-14T15:03:02 | 20022 | 4.90342 | 13880 | 8668 | GPServerSync.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.
Hi @JianLiu5
Can you please help to share your findings on this. Thank you.