Redux: Performance Comparison Between Process Builder and Apex Triggers

At the end of 2016, I posted about the performance differences between Process Builder and Apex Triggers on single record and bulk transactions (it’s a good read, check it out here).

Since it’s been over 18 months and Salesforce has been improving the platform with every release, can we prove it?

As a recap, our test scenario was somewhat contrived… when an Account is inserted with a name that starts with “Test”, Salesforce must create a new Contact and new Opportunity. For that Opportunity, there must exist 4 Opportunity Products.

With the same configuration (2 processes vs 1 trigger), the results are impressive.

TLDR: Process Builder gained efficiencies somewhere, and it’s nearly just as fast as Apex.

Process Builder was much slower than an Apex trigger back in December 2016, but has improved massively as of August 2018. If you’re interested in looking at the comparison data, check out this Google Sheet.

While Apex is still faster than Process Builder, the performance benefits may not be realized if your team either lacks development resources, or needs to rely on outside consulting partners. Feel free to tweet @RogerMitchell, leave a comment below, or silently forward this along to your admin and dev colleagues.

Shameless plug… if you’re interested in working with a consulting partner that appreciates when to use config and code that will scale for your organization, you may want to check out Dodge Labs!