Apex Code Governor Limits:
This list of governor limits does change from release to release - in particular many governor limits are simplified and the limits are sometimes raised. Below are a few Governor Limits.
Also Read: Why We Need To Follow The Apex Governor Limits?
- Total number of SOQL queries issued: 100
- Total number of SOQL queries issued for Batch Apex and future methods: 200
- Total number of records retrieved by SOQL queries: 50,000
- Total number of records retrieved by a single SOSL query: 200
- Total number of DML statements issued: 150
- Total number of records processed as a result of DML statements, Approval.process, or database.emptyRecycleBin: 10,000
- Total number of executed code statements: 200,000
- Total number of executed code statements for Batch Apex and future methods: 1,000,000
- Total heap size: 3 MB
- Total heap size for Batch Apex and future methods: 6 MB
- Total stack depth for any Apex invocation that recursively fires triggers due to insert, update, or delete statements: 16
- For loop list batch size: 200
- Total number of callouts (HTTP requests or Web services calls) in a request: 10
- Maximum timeout for all callouts (HTTP requests or Web services calls) in a request: 120 seconds
- Default timeout of callouts (HTTP requests or Web services calls) in a request: 10 seconds
- Total number of methods with the future annotation allowed per Apex invocation: 10
- Maximum size of callout request or response (HTTP request or Web services call): 3 MB
- Total number of sendEmail methods allowed: 10
- Total number of describes allowed: 100
- Maximum number of characters for a class: 1 million
- Maximum number of characters for a trigger: 1 million
- Maximum amount of code used by all Apex scripts in an organization: 2 MB
- If a SOQL query runs more than 120 seconds, the request can be canceled by Salesforce.
- Each Apex request is limited to 10 minutes of execution.
- A callout request to a given URL is limited to a maximum of 20 simultaneous requests.
- The maximum number of records that an event report returns for a user who is not a system administrator is 20,000, for system administrators, 100,000.
- Each organization is allowed 10 synchronous concurrent events, each not lasting longer than 5 seconds. If additional requests are made while 10 requests are running, it is denied.
- A user can have up to five query cursors open at a time. For example, if five cursors are open and a client application still logged in as the same user attempts to open a new one, the oldest of the five cursors is released.
- Cursor limits for different Force.com features are tracked separately. For example, you can have five Apex query cursors, five batch cursors, and five Visualforce cursors open at the same time.In a single transaction, you can only reference 10 unique namespaces. For example, suppose you have an object that executes a class in a managed package when the object is updated. Then that class updates a second object, which in turn executes a different class in a different package. Even though the second package wasn't accessed directly by the first, because it occurs in the same transaction, it's included in the number of namespaces being accessed in a single transaction.
For More about apex Governor limits -Visit DeveloperForce.com
