#SalesforceApexHours #FarmingtonHillsSFDCDug Agenda :- • Whats is HyperBatch • Difference between Old Traditional Apex Batch job and HyperBatch • Demo • FAQ

1. Farmington Hills Salesforce Developer User Group
Salesforce Apex Hours :- HyperBatch
#SalesforceApexHours
#FarmingtonHillsSFDCDug

2. Who am I ?
Amit Chaudhary
• Active on Salesforce Developer Community
• Blogging at http://amitsalesforce.blogspot.in/
• Co-Organizer of :- FarmingtonHillsSFDCDug
• @amit_sfdc
• Amit.salesforce21@gmail.com

3. Our Speaker
Daniel Peter
• Salesforce MVP
• 22x Certified
• Bay Area Salesforce Dev Group Leader
• Lead Application Engineer, Kenandy
• dan@danpeter.com
• @danieljpeter

4. Apex Database.Batchable

5. Why HyperBatch? Speed!
Case study: Account / Contact Batches
• Prerequisite: 121K Accounts already in the system
• CreateContactsBatch: Creates 3 Contacts for each Account with a random “probability” field for
each. 363k Contacts total.
• UpdateAccountsBatch: For each Account, update the highest and lowest probability on the
Account by querying the child Contacts. Get the overall highest and lowest probability across all
the Accounts.
• DeleteContactsBatch: Delete all of the Contacts in the system. Keep a running total of how many
get deleted.

6. Why HyperBatch? Speed!
CreateContactsBatch
▶ Using traditional Apex Database.Batchable: 45 mins

7. Why HyperBatch? Speed!
UpdateContactsBatch
▶ Using traditional Apex Database.Batchable: 10 mins

8. Why HyperBatch? Speed!
DeleteContactsBatch
▶ Using traditional Apex Database.Batchable: 33 mins total (got row lock errors, had to run twice)

9. Why HyperBatch? Speed!
CreateContactsHyperBatch
▶ Using HyperBatch:
▶ 2 mins 12 seconds

10. Why HyperBatch? Speed!
UpdateContactsHyperBatch
▶ Using HyperBatch:
▶ 55 seconds

11. Why HyperBatch? Speed!
DeleteContactsHyperBatch
▶ Using HyperBatch:
▶ 3 mins 15 seconds
▶ RowLock / retry
▶ 9500 Batch Size

12. Why HyperBatch? Speed!
Operation Database.Batchable HyperBatch Difference Percentage
CreateContacts 45 1.4 43.6 3.2%
UpdateContacts 10 0.9 9.1 9.9%
DeleteContacts 33 3.25 29.8 10.9%
Total 88 5.55 82.5 6.7%

13. Why HyperBatch? Speed!
Summary
▶ Running all 3 example batch jobs takes only 6 mins instead of 88 mins.
▶ You save 82 mins.
▶ It only takes 6.7% of the time!

14. Why HyperBatch? User Experience
Traditional Apex Batch HyperBatch

15. Why HyperBatch? Concurrency
▶ Asynchronous
▶ Apex Batch
▶ 5 running per org
▶ HyperBatch
▶ Not subject to 50 job per transaction limit (each request is a new transaction)
▶ Synchronous
▶ Apex Batch
▶ N/A
▶ HyperBatch
▶ 10 long running per org, unlimited otherwise

16. Why HyperBatch? Concurrency

17. Why HyperBatch? Concurrency
Row lock behavior
▶ Apex Batch: default is a failed batch execution. Retry logic can be built, but it will likely exceed
the transaction limits.
▶ HyperBatch: row locks retry automatically until the transaction succeeds. Each re-attempt gets a
new context!

18. How it Works - Summary
• HyperBatch interface that mimics the Database.Batchable interface.
• Browser orchestration for selecting jobs and running them on-demand.
• Lightning Design System, Visualforce (Lightning Components would be a data bottleneck).
• AJAX toolkit for PK chunking the query locator.
• Wrapping requests in unique identifiers for closed loop execution – JavaScript function binding.
• Each execute can return some state of type Object, it can be anything.
• Async
• Parallel remote actions fire the qeueables for the batch executions methods. (Not serial!)
• JavaScript polls for the status of the qeueables, waiting for them to complete.
• Execute state is stored in a custom object, and a list of them is returned to the finish() method, then they are deleted.
• Sync
• Parallel remote actions fire the synchronous transactions. (Not serial!)
• Execute state is returned synchronously and stored in JavaScript in the browser until they are all complete.

19. How it Works - Interface

20. How it Works – Asynchronous Architecture

21. How it Works – Synchronous Architecture

23. synchronous vs. asynchronous governor limits
Synchronous Asynchronous
SOQL Queries 100 200
Heap Size 6MB 12MB
CPU Time 10 seconds 60 seconds

24. Demo

25. New Features
• Synchronous mode
• Batch Size Control
• Test Methods

26. Roadmap
• Throttle requests (x number of open connections)
• Enhance the user interface
• Support custom iterators instead of just query locator
• Support simple data operations like update a field or delete records without having to write Apex
• Chunk in 2 dimensions: (Parent Id, then Record Id) to avoid row lock errors
• Sequence batches in series (run a batch after a batch)

27. Resources
• Salesforce Developer Blogs
• “Data Chunking Techniques for Massive Orgs“ by Daniel Peter
(https://developer.salesforce.com/blogs/developer-relations/2015/11/pk-chunking-techniques-massive-
orgs.html)
• “French Touch Dreamin’ – The first community-led event in France” by Philippe Ozil
(https://developer.salesforce.com/blogs/developer-relations/2016/11/french-touch-dreamin-first-
community-led-event-france.html)
• Presentation from Forcelandia 2016: “PK Chunking – Divide and conquer massive objects in
Salesforce” (http://www.slideshare.net/danieljpeter/forcelandia-2016-pk-chunking)
• GitHub repo: HyperBatch (https://github.com/danieljpeter/HyperBatch)

28. Thank You
Thank you for attending the session.

29. Follow Farmington Hills SFDC Developer Group
Twitter Hashtag
#FarmingtonHillsSFDCDug
Meetup.com
https://www.meetup.com/Farmington-Hills-Salesforce-Developer-Meetup/
Facebook Page
https://www.facebook.com/FarmingtonHillsSfdcdug/?ref=bookmarks