Resources > Performance Benchmarking Results > SFM Delivery — Performance Benchmarking
SFM Delivery — Performance Benchmarking
Test Environment Details
• Classic Scenarios: Both SFDC and Delivery in Classic
• React Scenarios: SFDC in Lightning and Delivery in React
• Delta lines added for SFM Save: New 10 child lines for every SFM save
• Network Details:
◦ Download Speed: ~570 Mbps
◦ Upload Speed: ~820 Mbps
◦ Latency: ~13ms
• Client Spec: 4 Processors and 8GB RAM
• Browser: Chrome
• Octane Score: ~27000
Configuration Settings
• GBL036 (SFM Query Optimizer) is set to True, and the default value is False
When this setting is True, loading an SFM is optimized by querying only those fields referenced in the SFM transaction. If a Web service or JavaScript code snippet requires fields that are not already available in the SFM, they have to be included in the SFM Fieldset.
• GBL043 (Enable cross-origin resource sharing) is set to False, the default value is False
This setting allows the code (such as JavaScript) running in a Web browser to communicate with Salesforce from a specific origin, whitelist the origin from the CORS page of Salesforce setup, and make this setting true.
Performance Benchmarking Metrics
SFM Transaction Type
Scenario
Response Time (in Seconds)
Classic
React
Create Case From IB
First Load
2.6
2.8
Subsequent Load
1.6
1.8
Save
2.3
3.9
Create Work Order From Case
First Load
2.5
2.8
Subsequent Load
1.5
1.7
Save
2.8
4.1
Work Order Debrief
First Load
4.5
8.5
Subsequent Load
2.6
7.4
Save
6.5
9.6
Work Order Debrief (Linked SFM)
First Load
7.5
8.4
Subsequent Load
5.3
7.1
Save
4.0
6.5
PM Work Order Debrief
First Load
5.6
6.8
Subsequent Load
3.0
5.4
Save
8.5
8.3
Contracts With Coverage
First Load
3.8
5.1
Subsequent Load
2.6
3.7
Save
6.9
8.1
PM Work Order Debrief (Linked SFM)
First Load
8.1
8.7
Subsequent Load
5.9
6.9
Save
4.9
6.6
Contracts With Coverage Renewal
First Load
4.2
5.9
Subsequent Load
2.7
4.6
Save
7.9
12.7
Work Order Debrief
First Load
4.1
4.9
Subsequent Load
2.1
3.4
Save
5.8
6.7
Was this helpful?