As an experienced Salesforce architect or developer, your job is as dynamic as your organization and its users. You don’t just need to design a sharing model, Force.com applications, and SOQL queries that meet your company’s current security, page performance, and data requirements; you must also design an architecture that can scale to support your organization’s future data volumes and user bases.
So why chance facing additional work and long wait times later, or wishing that you had a time-traveling Delorean to hop in? Just attend Technical Enablement’s sessions and workshops at Dreamforce to learn a few performance-related best practices, test what you learned in a hands-on environment, and scale your organization to success.
It’s important to understand what your customers are doing on your site. It’s even more important to understand how they’re using your site. If something goes wrong and the end user has a bad experience, it reflects poorly on the company. At salesforce.com we take this seriously. One of the main indicators we use to gauge if a customer is having a good experience is looking at how long it takes for a page of the Salesforce web application to load on the browser. We currently use an end user performance tool called jiffy to accomplish this. This post covers a version, called Kylie, we’re open sourcing and how we’re using it to influence current and future design of our product.
Every day, the Technical Enablement team works with customers like you to review their architectures and help them solve implementation challenges on the Salesforce platform. One of those implementation challenges involves a seemingly simple platform feature: formula fields. Under the hood, poorly designed formula fields can consume a lot of resources, lead to slow query response times, and hurt your users’ productivity.
We see these problems in many of our customer cases, and we know that the best way to avoid them involves learning both what makes formula fields efficient and how to build efficient formula fields. If you’re a developer, architect, or administrator who wants to build lightning-fast formula fields, you’ll want to attend our intermediate-level Dreamforce session, “Revving Up the Force.com Formula Engine,” and its associated workshop.
Agents widely use the Salesforce Console on a day-to-day basis while working with several entities like cases, accounts, leads etc. They spend almost the entire day within the console, opening and closing several tabs. Considering this, the end user performance of the application becomes vitally important. In this write-up, I have presented my observations when comparing the performance of the Salesforce Console in various browsers in a typical contact center environment.
One advantage of the Force.com platform is that it allows you to develop applications quickly and easily using both standard and custom features, such as custom Visualforce pages and Apex classes.
But how can you test whether your application can scale to meet the needs of your growing user base? The Force.com platform includes a framework for creating and running test classes, but when you need to account for larger volumes of data and more demanding application conditions, you might need to move a level beyond unit testing. This blog post helps you plan for growth by outlining your application testing options, explaining which ones you should use and when you should use them, and suggesting how you should work with salesforce.com Customer Support to maximize your tests’ effectiveness and value.
Does your salesforce.com implementation involve running reports or generating dashboards for a base object that has tens of millions of records? Do you have reports that aggregate data from more than one object? Or are your users’ dashboard refreshes timing out? This blog post will give you an overview of how to design reports for large data volumes (LDV).
In Blog: engineering
| Also tagged architecture, LDV
Performance profiling can help you proactively handle both the volumes of data and the complex sharing configurations that might grow alongside the size and success of your organization. You can use several performance profiling tools and resources to identify and fix performance bottlenecks, and one of those resources, Daisuke Kawamoto’s “A Guide to Application Performance Profiling in Force.com” article, was just published.
In Blog: engineering
| Also tagged architecture
If you have sales representatives closing opportunities, support representatives working through a list of cases, or even managers running reports, you’ll want to optimize query performance in your Force.com applications. In saleforce.com’s multitenant environment, the Force.com query optimizer does its own kind of optimization, generating the most efficient SQL from your SOQL, reports, and list views. This blog post explains the filter conditions and the Force.com query optimizer thresholds that determine the selectivity of your queries and affect your overall query performance.
You’ve been tasked with extracting data from a Salesforce object. If you’re dealing with small volumes of data, this operation might be simple, involving only a few button clicks using some of the great tools available on the AppExchange.
But when it comes to dealing with millions of records in a limited time frame, you might need to take extra steps to optimize the data throughput. Read this post to learn just what those steps are.
Do you know what types of requests count against the concurrent request limit? Learn to design applications that scale and avoid hitting this limit.