Resources > Performance Benchmarking Results > SFM Delivery — Performance Benchmarking in 23.1
SFM Delivery — Performance Benchmarking in 23.1
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: ~560 Mbps
Upload Speed: ~810 Mbps
Latency: ~8ms
Client Spec: 4 Processors and 8GB RAM
Browser: Chrome
Octane Score: ~24775
Configuration Settings
GBL036 (SFM Query Optimizer) set to True, default value is False
When this setting is True, loading an SFM is optimized by querying only those fields referenced in the SFM transaction. In case there is a Web-service or JavaScript code snippet that requires fields that are not already available in the SFM, they have to be included in the SFM Field set
GBL043 (Enable cross-origin resource sharing) set to False, 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 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
3.5
4.1
Subsequent Load
1.5
1.2
Save
3.2
3.7
Create Work Order From Case
First Load
3.4
4.6
Subsequent Load
1.5
1.3
Save
4.9
4.0
Work Order Debrief
First Load
5.9
10.8
Subsequent Load
3.2
7.8
Save
9.7
8.7
Work Order Debrief (Linked SFM)
First Load
9.5
9.6
Subsequent Load
6.6
6.7
Save
4.3
5.5
PM Work Order Debrief
First Load
5.6
9.3
Subsequent Load
2.7
5.8
Save
9.9
8.2
Contracts With Coverage
First Load
5.0
5.2
Subsequent Load
2.6
3.8
Save
8.4
8.8
PM Work Order Debrief (Linked SFM)
First Load
10.3
9.9
Subsequent Load
7.3
6.9
Save
5.0
5.6
Contracts With Coverage Renewal
First Load
4.8
6.1
Subsequent Load
2.9
5.4
Save
10.6
13.9
Work Order Debrief
First Load
4.2
6.7
Subsequent Load
1.6
3.2
Save
6.6
6.6
Was this helpful?