Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Optimizing Salesforce Industries Solutions on the Vlocity OmniStudio Platform

You're reading from   Optimizing Salesforce Industries Solutions on the Vlocity OmniStudio Platform Implementing OmniStudio best practices for achieving maximum performance

Arrow left icon
Product type Paperback
Published in Apr 2024
Publisher Packt
ISBN-13 9781835468470
Length 278 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Dmitri Khanine Dmitri Khanine
Author Profile Icon Dmitri Khanine
Dmitri Khanine
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1:The Platform Overview FREE CHAPTER
2. Chapter 1: Understanding the Vlocity OmniStudio Platform 3. Chapter 2: A Sample Application 4. Part 2: Getting to Know the Tools
5. Chapter 3: Evaluating the Performance of an OmniStudio Implementation 6. Chapter 4: An Introduction to Load Testing 7. Chapter 5: Tracking Code Changes and Deployment 8. Part 3: Best Practices for Improving Performance
9. Chapter 6: Options for Async Execution 10. Chapter 7: Understanding Caching 11. Chapter 8: Non-Selective Queries and Data Skew 12. Chapter 9: Improving the Performance of the Service Layer 13. Chapter 10: Improving the Performance of the Presentation Layer 14. Chapter 11: DataRaptor Formula Performance Considerations 15. Chapter 12: OmniStudio Performance Anti-Patterns 16. Index 17. Other Books You May Enjoy

Understanding data skew

If you are seeing update operations take a while and/or seeing UNABLE_TO_LOCK_ROW exceptions during inserts or updates, data skew issues could be the reason. Data skew is a database anti-pattern that occurs when a significant number of records are dependent on one single record. For instance, many Contacts are children of the same Account.

When a child record is then updated, the platform locks the parent to ensure data integrity during the update. Normally, this happens very fast and does not cause any issues. However, as data volumes grow, updating children of the same parent may become very slow and, when done in different threads, some of the updates may fail.

Salesforce recommends keeping the number of child records related to the same parent under 10,000 to avoid performance and locking issues. So, if you must relate many child records to the same parent, create additional parents to keep the number of children under 10,000. You may also want to...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime