Apex Performance Troubleshooting
Force.com is a platform where you can build compelling applications using Visualforce and Apex. However, sometimes you’ll find yourself dealing with unexpected performance problems in your app that impact the user experience. Troubleshooting Apex performance problems can be difficult and time-consuming, so it’s worth understanding the causes and ways to fix any issues that come up.
We’ve created an article that talks about what can cause Apex performance problems, ways to diagnose these problems, and tools to help you quickly and easily get the information you need. In particular, the article discusses how to work with Apex debug logs, including understanding log time gaps and how overuse of System.Debug can affect logs. Additionally, the article talks about an Apex Timeline tool that uses the Tooling API to programmatically access debug logs.
Armed with this knowledge, you’ll be able to track down Apex performance issues in no time, and make your app fly!
- Troubleshooting Apex Performance Problems
- Understanding the Debug Log
- Working with Logs in the Developer Console
- Force.com Performance Profiling Using the Developer Console
- Monitoring Debug Logs
- Setting Debug Log Filters
- Debug Log Filtering
- Authenticating Apps with OAuth
- Digging Deeper into OAuth 2.0 on Force.com
- Tooling API Developer’s Guide
About the Author and CCE Technical Enablement
Dan Yu is a technical writer within the Technical Enablement team of the salesforce.com Customer-Centric Engineering group. The team’s mission is to help customers understand how to implement technically sound salesforce.com solutions. Check out all of the resources that this team maintains on the Architect Core Resources page of Developer Force.