Governor limits in Salesforce enforce runtime limits on Apex code to ensure fair sharing of system resources among multiple tenants. The key governor limits include limits on the number of SOQL queries, records retrieved, and number of scripts executed. Governor limits are calculated based on the entry point for the Apex code, such as Apex triggers, web services, or anonymous blocks. Limits are shared across an organization and apply to all code executed within a synchronous transaction, while asynchronous code like future methods has separate limits. Developers must optimize code to avoid hitting governor limits, for example by bulkifying code, minimizing SOQL queries, and using future calls appropriately.

1. In depth view of the governor limits in apex SalesForce
SHIVANATH.D

2. What are Governor Limits ?
• Runtime limits enforced by apex
• Ensures no monopoly in resources.
Memory
• Similar to heap size in Java.
• Back bone of MULTI-TENANT
architecture. Database Resources
• The Organization Shares the limit
No of Script Statements
No of Records processed

3. How are Governor Limits Calculated?
There are a number of factors that
determine what governor limit is
used, and when it is applied
Invocation of Apex-Entry
How Many Records
Which Governor Limit

4. Entry Point
• Governor limits are applied based
on the entry point Apex Trigger
•insert, update, delete, merge,
upsert, and undelete are the Trigger
Apex Web service
operations
• All Apex triggers are bulk triggers.
• Batch of up to 200 records Anonymous Block
• Anonymous block does not get
stored in the metadata Visualforce Controller
•Run Tests is a Force.com Web
Services API call used to execute test
methods Run Tests

5. Governor Limit Scope
• Governor Limits are shared by the
organization
Maximum of 100 SOQL Queries
•From beginning till end of
execution
Max of 50,000rows retrieved
•Governor limits are not specified for
each separate trigger. Max of 200,000 scripts executed
•Any Apex class, method, or trigger
invoked by code executed within the Max 50 million Batch SOQL
entry point will count towards the
same governor limits as it's a Batches of up to 2,000 records
synchronous request

6. Synchronous vsAsynchronous Apex
• Normal Execution Synchronous
•@future is asynchronous
Synchronous
•Business Logic is offloaded
•Efficiency increases
• but , more callouts
VS
Asynchronous

8. Limits
SOQL statements issued in a request.
Database.countQuery
Database.getQueryLocator
Database.query
DML queries issued in a request.
Approval.process
Database.convertLead
Database.emptyRecycleBin
Database.rollback
Database.setSavePoint
delete and Database.delete
insert and Database.insert
merge
undelete and Database.undelete
update and Database.update
upsert and Database.upsert
System.runAs

9. Bulkify your Code
Poorly Written Code
Bulkified Code

10. Avoid SOQL Queries inside FOR Loops

11. Avoid SOQL Queries inside FOR Loops

12. Use Collections in code

13. Streamlining Multiple Triggers on the
Same Object
• Merge if triggers are redundant
• Triggers same share limit
• Easy to hit the governor limits

14. Querying Large Data Sets

15. Use @futureAppropriately
Don’t do this !

16. Q &A