SAP CRM Fiori My Opportunity应用的性能分析

1: #8 in excel

[https://fiorilaunchpad-faasperf.dispatcher.neo.ondemand.com/sap/opu/odata/sap/CRM_OPPORTUNITY/Opportunities?]{.underline}$skip=0&$top=20&$inlinecount=allpages

This roundtrip is used to render the navigation list when the Opportunity tile is clicked by launchpad. It is mandatory, could not be eliminated.

2: #11: [https://fiorilaunchpad-faasperf.dispatcher.neo.ondemand.com/sap/opu/odata/sap/CRM_OPPORTUNITY/]{.underline}

Once the top 20 opportunities are retrieved from backend, by default the FIRST item in the navigation list will be selected automatically, and its detail data will be displayed in the detail view ( technical name: S3.view.xml ). Thus the detailed data of this selected opportunity will be fetched via OData batch request (roundtrip marked with green in below picture - this is however the #13 roundtrip mentioned in the excel).

Before this batch request is really sent to backend, OData framework will issue a token request refresh operation first:

Detail operation of this roundtrip:

And new CSRF token is returned and contained in HTTP response header:

Summary: this roundtrip is issued by OData handling framework and thus could not be controlled by application:

3: #13 roundtrip - just the batch request mentioned in step2:

–batch_c9c9-beb3-1a6d

Content-Type: application/http

Content-Transfer-Encoding: binary

GET SalesStages HTTP/1.1

Accept-Language: en

Accept: application/json

MaxDataServiceVersion: 2.0

DataServiceVersion: 2.0

–batch_c9c9-beb3-1a6d

Content-Type: application/http

Content-Transfer-Encoding: binary

GET Priorities HTTP/1.1

Accept-Language: en

Accept: application/json

MaxDataServiceVersion: 2.0

DataServiceVersion: 2.0

–batch_c9c9-beb3-1a6d

Content-Type: application/http

Content-Transfer-Encoding: binary

GET UserStatuses HTTP/1.1

Accept-Language: en

Accept: application/json

MaxDataServiceVersion: 2.0

DataServiceVersion: 2.0

–batch_c9c9-beb3-1a6d

Content-Type: application/http

Content-Transfer-Encoding: binary

GET Currencies HTTP/1.1

Accept-Language: en

Accept: application/json

MaxDataServiceVersion: 2.0

DataServiceVersion: 2.0

–batch_c9c9-beb3-1a6d

Content-Type: application/http

Content-Transfer-Encoding: binary

GET Opportunities(guid’FA163EEF-573D-1ED4-BEC1-5BEA665821F3’)?$expand=ChangeDocs,Competitors,Products,OpportunityLogSet HTTP/1.1

Accept-Language: en

Accept: application/json

MaxDataServiceVersion: 2.0

DataServiceVersion: 2.0

–batch_c9c9-beb3-1a6d

Content-Type: application/http

Content-Transfer-Encoding: binary

GET RetrieveMaxHitSet HTTP/1.1

Accept-Language: en

Accept: application/json

MaxDataServiceVersion: 2.0

DataServiceVersion: 2.0

–batch_c9c9-beb3-1a6d–

Instance based.

4: #12 roundtrip [https://fiorilaunchpad-faasperf.dispatcher.neo.ondemand.com/sap/opu/odata/sap/CRM_OPPORTUNITY/Opportunities(guid]{.underline}

This roundtrip is used to get ETAG:

ETAG returned in http response header:

Instance based.

5: #14 roundtrip: [https://fiorilaunchpad-]{.underline}

faasperf.dispatcher.neo.ondemand.com/sap/opu/odata/sap/CRM_OPPORTUNITY/AccountCollection(‘3272’)?$expand=Logo

This roundtrip is responsible to retrieve the logo header information of a given account. Logo is maintained in CRM backend system via attachment.

6. #15 roundtrip: [https://fiorilaunchpad-faasperf.dispatcher.neo.ondemand.com/sap/opu/odata/sap/CRM_OPPORTUNITY/AttachmentCollection(documentID=]{.underline}/$value

The document id and document class are retrieved by the previous roundtrip, #14. Then the binary data of logo image is retrieved in this step.

The data retrieve for logo image binary data is expensive. Just checked in SAP internal system, for a small image with 16.8k, still more than 800ms is spent in backend handling.