Salesforce built a scalable performance engineering team by establishing engineer to developer ratios, embedding performance testing into scrum teams, developing extensive automation frameworks and test environments, and creating synthetic workloads that mimic real-world production traffic shapes and loads to thoroughly test new features and identify performance issues. The performance engineering team works closely with development teams throughout the release process to catch issues early and optimize performance.
Building a Center of Excellence for your Salesforce crm teamBuyan Thyagarajan
1) The documents discuss key components of a successful business transformation including governance, roles and responsibilities within a Center of Excellence (COE), and cultural principles for the COE.
2) It provides examples of COE organizational structures and recommends having clear processes for program management, architecture, adoption, development, and release management.
3) Establishing principles like being mobile-first, configuration over custom code, and making decisions based on data are emphasized as helping the COE move quickly while driving business value.
Learn from the Experts: Using DORA Metrics to Accelerate Value Stream FlowDevOps.com
This document outlines a webinar on using DORA metrics to accelerate value stream flow. The webinar will be led by Helen Beal and Jeff Keyes and will discuss why measuring performance is important, what the DORA metrics are, insights into optimizing flow, and how to manage value streams. Key aspects that will be covered include culture, automation, lean principles, measurement, sharing best practices, lead time, cycle time, deployment frequency, change fail rate, mean time to restore service, value stream mapping, and value stream management platforms and tools.
1) DevOps aims to automate and integrate processes between software development and IT teams to increase efficiency. It emphasizes cross-team communication and technology automation.
2) When adopting Salesforce DevOps, organizations face challenges around lack of best practices, admin-friendliness of tools, complexity of Salesforce environments, and finding expertise.
3) There are two main approaches to Salesforce DevOps - building out a solution using Salesforce tools like DX and scripting, or buying an ISV solution. Building provides more flexibility while buying provides pre-built features and support.
Sandboxes provide environments for development, testing, and training that are isolated from production. There are different types of sandboxes that serve different purposes - Developer sandboxes refresh daily and don't include data, while Partial Copy and Full Copy sandboxes include production data and configurations and refresh less frequently. Choosing the right sandbox type depends on factors like the need for data, external integration testing requirements, and user acceptance testing needs. Sandboxes allow changes to be tested safely before moving to production.
Dreamforce 2014 Presentation : Salesforce.com Sandbox management
Large organizations have complex development processes that span multiple release schedules. It is not only the division between development and testing that is important, but the synchronization of projects on different schedules.
This document discusses modernizing applications for the cloud. It outlines different paths like rehosting, refactoring, or rearchitecting applications using containers, microservices, and serverless architectures. It also discusses the importance of DevOps practices and using Azure services to assess applications, create migration roadmaps, and continuously deliver updates. Migrating applications to Azure IaaS can reduce costs while refactoring or rearchitecting can enable new capabilities and improve scalability.
You and your colleagues are all doing great things with Splunk. But you seldom come together to share ideas, apps and best practices. This session will help you take Splunk to the next level by helping you establish a Splunk Center of Excellence (CoE) at your organization. The purpose of a COE is simple - to provide Splunk users an informal venue in which they can discuss ideas, diagnose challenges, share innovations and network with peers. This session will share the best practices you need to create and maintain a successful CoE practice.
Building a Center of Excellence for your Salesforce crm teamBuyan Thyagarajan
1) The documents discuss key components of a successful business transformation including governance, roles and responsibilities within a Center of Excellence (COE), and cultural principles for the COE.
2) It provides examples of COE organizational structures and recommends having clear processes for program management, architecture, adoption, development, and release management.
3) Establishing principles like being mobile-first, configuration over custom code, and making decisions based on data are emphasized as helping the COE move quickly while driving business value.
Learn from the Experts: Using DORA Metrics to Accelerate Value Stream FlowDevOps.com
This document outlines a webinar on using DORA metrics to accelerate value stream flow. The webinar will be led by Helen Beal and Jeff Keyes and will discuss why measuring performance is important, what the DORA metrics are, insights into optimizing flow, and how to manage value streams. Key aspects that will be covered include culture, automation, lean principles, measurement, sharing best practices, lead time, cycle time, deployment frequency, change fail rate, mean time to restore service, value stream mapping, and value stream management platforms and tools.
1) DevOps aims to automate and integrate processes between software development and IT teams to increase efficiency. It emphasizes cross-team communication and technology automation.
2) When adopting Salesforce DevOps, organizations face challenges around lack of best practices, admin-friendliness of tools, complexity of Salesforce environments, and finding expertise.
3) There are two main approaches to Salesforce DevOps - building out a solution using Salesforce tools like DX and scripting, or buying an ISV solution. Building provides more flexibility while buying provides pre-built features and support.
Sandboxes provide environments for development, testing, and training that are isolated from production. There are different types of sandboxes that serve different purposes - Developer sandboxes refresh daily and don't include data, while Partial Copy and Full Copy sandboxes include production data and configurations and refresh less frequently. Choosing the right sandbox type depends on factors like the need for data, external integration testing requirements, and user acceptance testing needs. Sandboxes allow changes to be tested safely before moving to production.
Dreamforce 2014 Presentation : Salesforce.com Sandbox management
Large organizations have complex development processes that span multiple release schedules. It is not only the division between development and testing that is important, but the synchronization of projects on different schedules.
This document discusses modernizing applications for the cloud. It outlines different paths like rehosting, refactoring, or rearchitecting applications using containers, microservices, and serverless architectures. It also discusses the importance of DevOps practices and using Azure services to assess applications, create migration roadmaps, and continuously deliver updates. Migrating applications to Azure IaaS can reduce costs while refactoring or rearchitecting can enable new capabilities and improve scalability.
You and your colleagues are all doing great things with Splunk. But you seldom come together to share ideas, apps and best practices. This session will help you take Splunk to the next level by helping you establish a Splunk Center of Excellence (CoE) at your organization. The purpose of a COE is simple - to provide Splunk users an informal venue in which they can discuss ideas, diagnose challenges, share innovations and network with peers. This session will share the best practices you need to create and maintain a successful CoE practice.
Salesforce – Proven Platform Development with DevOps & AgileSai Jithesh ☁️
The document discusses forward-looking statements and associated risks and uncertainties. It states that any projections or statements regarding strategies, plans, beliefs, expected functionality, features, or customer contracts contain forward-looking statements that are subject to risks and uncertainties. These risks include factors that could affect salesforce.com's financial results such as operating losses, fluctuations in results, security breaches, litigation outcomes, mergers and acquisitions, growth management, and reliance on key personnel. The document also notes that unreleased services mentioned may not be delivered on time or at all, and purchase decisions should be based on currently available features.
The document discusses the growth of Site Reliability Engineering (SRE) at Squarespace from a team of 2 people in New York to a global organization with teams in New York, Portland, and Dublin. It describes how the initial SRE team focused on three pillars: monitoring and alerting, configuration management, and builds and deploys. It then explains how the SRE organization expanded to include additional teams focused on areas like provisioning, release engineering, developer productivity, and observability while also embedding SREs within product teams.
The document outlines a phased approach to creating a center of excellence for DevOps. It discusses defining the strategy, designing the base, building the service, working with customers, and continual service improvement. The strategy phase involves understanding market needs, identifying goals, and planning resources. The design phase defines the scope of services, goals, and sets up teams. The building phase recruits and trains staff, creates practice labs, and collaborates with vendors. The customer phase communicates offerings and coordinates activities. The improvement phase aligns services with changing needs through training and service enhancements. The future holds moving DevOps to hyperspeed on cloud platforms.
SRE (service reliability engineer) on big DevOps platform running on the clou...DevClub_lv
SRE (service reliability engineer). The talk is to explain the SRE philosophy and the principles of production engineering and operations in clouds.
(Language – English)
Pavlo is ADOP (Accenture DevOps Platform) Service Reliability Team Lead, SRE practitioner. Has more then 18 years of IT experience in Ops and Dev.
Organisations using Salesforce will inevitably accumulate technical debt over time. It’s a costly side effect of growth, and to manage it successfully, these organisations need to not only remove their existing debt but also understand its causes and develop a plan to manage it in the future.
To find out more about the key areas you need to cover to carry out a successful technical debt assessment in the Salesforce platform watch our on-demand webinar:
https://www.whishworks.com/event/recording-performing-a-successful-technical-debt-assessment-in-salesforce/
Key topics
– What is technical debt
– Causes of technical debt in Salesforce
– Key areas to assess
– Common tools for diagnosis
– Technical debt assessment results & reporting
Site Reliability Engineering (SRE) - Tech Talk by Keet SugathadasaKeet Sugathadasa
When it comes to Site Reliability Engineering, short for SRE, the resources available online are only limited to the books published by Google themselves. They do share some useful case studies that will help us understand what SRE is, and how to understand the concepts given in it, but they do not clearly explain how to build your own SRE team for your organization. The concept of SRE was cooked fresh within the walls of Google and later released to the general public as a practice for anyone to follow.
In this presentation I would like to give a brief introduction to SRE and why it is important to any Software Engineering organization. This is based on my experiences and learnings from leading a Site Reliability Engineering team for leading organizations in the US and Norway.
This presentation was conducted by me as a Tech Talk as an Associate Technical Lead at Creative Software Sri Lanka.
Presented at French Touch Dreamin 2019. This topic is to show you the key elements to take care of in order to deliver Salesforce projects successfully, taking the advantages of the latest Salesforce tools.
This document provides an overview of site reliability engineering (SRE). It discusses that SREs work to keep sites up, know the production environment, and help build infrastructure for monitoring, deployment, and automation. Hiring SREs can help improve uptime and utilize their experience from similar systems at scale. SREs should be involved in discussions affecting the production environment and help make software more reliable and fault-tolerant.
While there are many ways to build integrations with salesforce, one of the fastest growing ways is through the Salesforce REST API. Join us as we explore the current REST-ful mechanisms available to the AppCloud, and see what the next year has to offer. In this session we will discuss the Salesforce REST API structure, Authenticating to the REST API, sObject Manipulation, and Composition through the REST API.
Marlabs Infrastructure Services practice partners with enterprises enabling them to maximize their IT investments and focus their activities on initiatives that drive business innovation. Leveraging our enterprise class data centers, deep technical capabilities, comprehensive tool sets, operational best practices, and security standards we manage the day to day operations of running our clients IT environment at peak performance without compromising the confidentiality, availability and integrity of data entrusted by them. Our ‘OneConsole’ is a unified service and operations management platform providing a single pane of glass for enterprises to provision, monitor, secure, and govern IT services on premise, Cloud, or both.
DevOps & Cloud - The Essentials for Digital TransformationCloudJourneee
Learn how DevOps and Cloud can help in Digital Transformation. The deck covers:
Digital Transformation - The Current Organizational Scenario
Understanding the DevOps – Cloud Relationship
Building & Managing Cloud Applications with DevOps
Use Cases
Benefits of Moving to Cloud with DevOps
Using Personas for Salesforce Accessibility and SecuritySalesforce Admins
The document provides an overview of using personas for Salesforce permissions and security configurations. It discusses how personas can group users based on shared behaviors, goals, and tasks to help design more targeted security profiles and permission sets. The speakers then provide examples of two personas - a "Pipeline Builder" and "Deal Closer" - and how their different behaviors and tasks would translate to customized security configurations and sharing rules. Resources for learning more about personas and Salesforce security best practices are also listed.
Asynchronous Apex Salesforce World Tour Paris 2015Samuel De Rycke
The document discusses asynchronous Apex processing in Salesforce, including batch Apex, future methods, queueable Apex, scheduled Apex, and continuations. It describes when each would be used and how they allow processing to continue asynchronously rather than blocking the current transaction. It also provides examples of how to implement each type of asynchronous processing and notes some limitations, such as concurrent jobs limits and parameter passing restrictions.
Planning Your Migration to the Lightning ExperienceShell Black
Learn how to migrate to the Salesforce Lighting UI in four steps. Shell Black in this presentation discusses how to make the business case to justify the costs to moving to the Lightning Experience (LEX) from Classic. In the four steps Shell covers how to assess the current state of your org, plan out the migration, manage your build sprints and UAT (User Acceptance Testing), and train your end users. He also covers the factors that drive the time needed to complete the project. As you will find, the biggest hurdle to migrating to Lightning is not a missing feature, but Admin knowledge. Click the link on Slide 2 to watch a video of this presentation!
Speaker: Anu Vijayamohan
Host: Angel Alberici
VirtualMuleys: 66 - 20220304-April
Recording & Slides: https://meetups.mulesoft.com/events/details/mulesoft-online-group-english-presents-mulesoft-sizing-guidelines/
All Recordings & Slides: meetups.mulesoft.com/online-group-english/ & youtube.com/c/VirtualMuleysOnline/videos
In this session we will discuss:
Core concepts of sizing
Factors that impact mule sizing
T-Shirt sizing
Sizing nuances in Cloudhub vs OnPrem vs RTF
High Availability
Master Continuous Delivery with CloudBees Jenkins Platformdcjuengst
This document discusses the CloudBees Jenkins Platform for continuous delivery. It begins by outlining challenges that organizations face as their use of open source Jenkins grows. It then introduces the CloudBees Jenkins Platform as an enterprise-grade solution for Jenkins that provides features like high availability, security, scalability, and expert support. The document explores various components of the CloudBees Jenkins Platform, including CloudBees Jenkins Enterprise, support for cloud and containers, continuous delivery capabilities, and tools for monitoring and management at scale.
Salesforce Application Lifecycle Management presented to EA Forum by Sam Garf...Sam Garforth
Sam Garforth presented this at the Salesforce Enterprise Architect Forum on January 12th 2017. It covers governance and best practices for developing, deploying and supporting applications running on the Salesforce platform, whether these be apps or configurations of Sales or Service Cloud or Communities.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1awkL99.
Details on Pinterest's architeture, its systems -Pinball, Frontdoor-, and stack - MongoDB, Cassandra, Memcache, Redis, Flume, Kafka, EMR, Qubole, Redshift, Python, Java, Go, Nutcracker, Puppet, etc. Filmed at qconsf.com.
Yash Nelapati is an infrastructure engineer at Pinterest where he focusses on scalability, capacity planning and architecture. Prior to Pinterest he was into web development and rapidly prototyping UI. Marty Weiner joined Pinterest in early 2011 as the 2nd engineer. Previously worked at Azul Systems as a VM engineer focused on building/improving the JIT compilers in HotSpot.
DevOps Transformation: Learnings and Best PracticesQBurst
The presentation delves into the best practices and approach for DevOps adoption. Understand key aspects of DevOps and how it brings about speed and efficiency in the software development lifecycle
The document discusses developing an effective engineering strategy. It recommends reviewing business strategies and objectives, understanding customer needs, and thoroughly analyzing the current engineering organization before developing the strategy. The engineering strategy should include visions, missions, objectives, key strategies, positioning statements, SWOT analysis, required capabilities, initiatives aligned with strategies, and strategic actions aligned with initiatives. The strategy aims to align engineering resources with business goals to enable growth while controlling costs.
Following best practices can help ensure your success. This is especially true for Force.com applications or large Salesforce orgs that have the potential to push platform limits.
Salesforce allows you to easily scale up from small to large amounts of data. Mostly this is seamless, but as data sets get larger, the time required for certain operations may grow too. Join us to learn different ways of designing and configuring data structures and planning a deployment process to significantly reduce deployment times and achieve operational efficiency.
Watch this webinar to:
:: Explore best practices for the design, implementation, and maintenance phases of your app's lifecycle.
:: Learn how seemingly unrelated components can affect one another and determine the ultimate scalability of your app.
:: See live demos that illustrate innovative solutions to tough challenges, including the integration of an external data warehouse using Force.com Canvas.
:: Walk away with practical tips for putting best practices into action.
Intended Audience
This webinar is perfect for Salesforce or Force.com architects and developers that want to better understand data management best practices to ensure both short and long-term implementation success. Although many topics focus on large data volumes, the recommendations in this presentation are equally relevant to smaller orgs.
Salesforce – Proven Platform Development with DevOps & AgileSai Jithesh ☁️
The document discusses forward-looking statements and associated risks and uncertainties. It states that any projections or statements regarding strategies, plans, beliefs, expected functionality, features, or customer contracts contain forward-looking statements that are subject to risks and uncertainties. These risks include factors that could affect salesforce.com's financial results such as operating losses, fluctuations in results, security breaches, litigation outcomes, mergers and acquisitions, growth management, and reliance on key personnel. The document also notes that unreleased services mentioned may not be delivered on time or at all, and purchase decisions should be based on currently available features.
The document discusses the growth of Site Reliability Engineering (SRE) at Squarespace from a team of 2 people in New York to a global organization with teams in New York, Portland, and Dublin. It describes how the initial SRE team focused on three pillars: monitoring and alerting, configuration management, and builds and deploys. It then explains how the SRE organization expanded to include additional teams focused on areas like provisioning, release engineering, developer productivity, and observability while also embedding SREs within product teams.
The document outlines a phased approach to creating a center of excellence for DevOps. It discusses defining the strategy, designing the base, building the service, working with customers, and continual service improvement. The strategy phase involves understanding market needs, identifying goals, and planning resources. The design phase defines the scope of services, goals, and sets up teams. The building phase recruits and trains staff, creates practice labs, and collaborates with vendors. The customer phase communicates offerings and coordinates activities. The improvement phase aligns services with changing needs through training and service enhancements. The future holds moving DevOps to hyperspeed on cloud platforms.
SRE (service reliability engineer) on big DevOps platform running on the clou...DevClub_lv
SRE (service reliability engineer). The talk is to explain the SRE philosophy and the principles of production engineering and operations in clouds.
(Language – English)
Pavlo is ADOP (Accenture DevOps Platform) Service Reliability Team Lead, SRE practitioner. Has more then 18 years of IT experience in Ops and Dev.
Organisations using Salesforce will inevitably accumulate technical debt over time. It’s a costly side effect of growth, and to manage it successfully, these organisations need to not only remove their existing debt but also understand its causes and develop a plan to manage it in the future.
To find out more about the key areas you need to cover to carry out a successful technical debt assessment in the Salesforce platform watch our on-demand webinar:
https://www.whishworks.com/event/recording-performing-a-successful-technical-debt-assessment-in-salesforce/
Key topics
– What is technical debt
– Causes of technical debt in Salesforce
– Key areas to assess
– Common tools for diagnosis
– Technical debt assessment results & reporting
Site Reliability Engineering (SRE) - Tech Talk by Keet SugathadasaKeet Sugathadasa
When it comes to Site Reliability Engineering, short for SRE, the resources available online are only limited to the books published by Google themselves. They do share some useful case studies that will help us understand what SRE is, and how to understand the concepts given in it, but they do not clearly explain how to build your own SRE team for your organization. The concept of SRE was cooked fresh within the walls of Google and later released to the general public as a practice for anyone to follow.
In this presentation I would like to give a brief introduction to SRE and why it is important to any Software Engineering organization. This is based on my experiences and learnings from leading a Site Reliability Engineering team for leading organizations in the US and Norway.
This presentation was conducted by me as a Tech Talk as an Associate Technical Lead at Creative Software Sri Lanka.
Presented at French Touch Dreamin 2019. This topic is to show you the key elements to take care of in order to deliver Salesforce projects successfully, taking the advantages of the latest Salesforce tools.
This document provides an overview of site reliability engineering (SRE). It discusses that SREs work to keep sites up, know the production environment, and help build infrastructure for monitoring, deployment, and automation. Hiring SREs can help improve uptime and utilize their experience from similar systems at scale. SREs should be involved in discussions affecting the production environment and help make software more reliable and fault-tolerant.
While there are many ways to build integrations with salesforce, one of the fastest growing ways is through the Salesforce REST API. Join us as we explore the current REST-ful mechanisms available to the AppCloud, and see what the next year has to offer. In this session we will discuss the Salesforce REST API structure, Authenticating to the REST API, sObject Manipulation, and Composition through the REST API.
Marlabs Infrastructure Services practice partners with enterprises enabling them to maximize their IT investments and focus their activities on initiatives that drive business innovation. Leveraging our enterprise class data centers, deep technical capabilities, comprehensive tool sets, operational best practices, and security standards we manage the day to day operations of running our clients IT environment at peak performance without compromising the confidentiality, availability and integrity of data entrusted by them. Our ‘OneConsole’ is a unified service and operations management platform providing a single pane of glass for enterprises to provision, monitor, secure, and govern IT services on premise, Cloud, or both.
DevOps & Cloud - The Essentials for Digital TransformationCloudJourneee
Learn how DevOps and Cloud can help in Digital Transformation. The deck covers:
Digital Transformation - The Current Organizational Scenario
Understanding the DevOps – Cloud Relationship
Building & Managing Cloud Applications with DevOps
Use Cases
Benefits of Moving to Cloud with DevOps
Using Personas for Salesforce Accessibility and SecuritySalesforce Admins
The document provides an overview of using personas for Salesforce permissions and security configurations. It discusses how personas can group users based on shared behaviors, goals, and tasks to help design more targeted security profiles and permission sets. The speakers then provide examples of two personas - a "Pipeline Builder" and "Deal Closer" - and how their different behaviors and tasks would translate to customized security configurations and sharing rules. Resources for learning more about personas and Salesforce security best practices are also listed.
Asynchronous Apex Salesforce World Tour Paris 2015Samuel De Rycke
The document discusses asynchronous Apex processing in Salesforce, including batch Apex, future methods, queueable Apex, scheduled Apex, and continuations. It describes when each would be used and how they allow processing to continue asynchronously rather than blocking the current transaction. It also provides examples of how to implement each type of asynchronous processing and notes some limitations, such as concurrent jobs limits and parameter passing restrictions.
Planning Your Migration to the Lightning ExperienceShell Black
Learn how to migrate to the Salesforce Lighting UI in four steps. Shell Black in this presentation discusses how to make the business case to justify the costs to moving to the Lightning Experience (LEX) from Classic. In the four steps Shell covers how to assess the current state of your org, plan out the migration, manage your build sprints and UAT (User Acceptance Testing), and train your end users. He also covers the factors that drive the time needed to complete the project. As you will find, the biggest hurdle to migrating to Lightning is not a missing feature, but Admin knowledge. Click the link on Slide 2 to watch a video of this presentation!
Speaker: Anu Vijayamohan
Host: Angel Alberici
VirtualMuleys: 66 - 20220304-April
Recording & Slides: https://meetups.mulesoft.com/events/details/mulesoft-online-group-english-presents-mulesoft-sizing-guidelines/
All Recordings & Slides: meetups.mulesoft.com/online-group-english/ & youtube.com/c/VirtualMuleysOnline/videos
In this session we will discuss:
Core concepts of sizing
Factors that impact mule sizing
T-Shirt sizing
Sizing nuances in Cloudhub vs OnPrem vs RTF
High Availability
Master Continuous Delivery with CloudBees Jenkins Platformdcjuengst
This document discusses the CloudBees Jenkins Platform for continuous delivery. It begins by outlining challenges that organizations face as their use of open source Jenkins grows. It then introduces the CloudBees Jenkins Platform as an enterprise-grade solution for Jenkins that provides features like high availability, security, scalability, and expert support. The document explores various components of the CloudBees Jenkins Platform, including CloudBees Jenkins Enterprise, support for cloud and containers, continuous delivery capabilities, and tools for monitoring and management at scale.
Salesforce Application Lifecycle Management presented to EA Forum by Sam Garf...Sam Garforth
Sam Garforth presented this at the Salesforce Enterprise Architect Forum on January 12th 2017. It covers governance and best practices for developing, deploying and supporting applications running on the Salesforce platform, whether these be apps or configurations of Sales or Service Cloud or Communities.
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1awkL99.
Details on Pinterest's architeture, its systems -Pinball, Frontdoor-, and stack - MongoDB, Cassandra, Memcache, Redis, Flume, Kafka, EMR, Qubole, Redshift, Python, Java, Go, Nutcracker, Puppet, etc. Filmed at qconsf.com.
Yash Nelapati is an infrastructure engineer at Pinterest where he focusses on scalability, capacity planning and architecture. Prior to Pinterest he was into web development and rapidly prototyping UI. Marty Weiner joined Pinterest in early 2011 as the 2nd engineer. Previously worked at Azul Systems as a VM engineer focused on building/improving the JIT compilers in HotSpot.
DevOps Transformation: Learnings and Best PracticesQBurst
The presentation delves into the best practices and approach for DevOps adoption. Understand key aspects of DevOps and how it brings about speed and efficiency in the software development lifecycle
The document discusses developing an effective engineering strategy. It recommends reviewing business strategies and objectives, understanding customer needs, and thoroughly analyzing the current engineering organization before developing the strategy. The engineering strategy should include visions, missions, objectives, key strategies, positioning statements, SWOT analysis, required capabilities, initiatives aligned with strategies, and strategic actions aligned with initiatives. The strategy aims to align engineering resources with business goals to enable growth while controlling costs.
Following best practices can help ensure your success. This is especially true for Force.com applications or large Salesforce orgs that have the potential to push platform limits.
Salesforce allows you to easily scale up from small to large amounts of data. Mostly this is seamless, but as data sets get larger, the time required for certain operations may grow too. Join us to learn different ways of designing and configuring data structures and planning a deployment process to significantly reduce deployment times and achieve operational efficiency.
Watch this webinar to:
:: Explore best practices for the design, implementation, and maintenance phases of your app's lifecycle.
:: Learn how seemingly unrelated components can affect one another and determine the ultimate scalability of your app.
:: See live demos that illustrate innovative solutions to tough challenges, including the integration of an external data warehouse using Force.com Canvas.
:: Walk away with practical tips for putting best practices into action.
Intended Audience
This webinar is perfect for Salesforce or Force.com architects and developers that want to better understand data management best practices to ensure both short and long-term implementation success. Although many topics focus on large data volumes, the recommendations in this presentation are equally relevant to smaller orgs.
Building High Performance Engineering Teams - Focus on People - Scrum Austral...Nicholas Muldoon
Twitter has grown from a handful of engineers to over a 1,000 in a few years. To be successful at such a scale requires finding the right people and making sure they are productive and solving valuable customer problems.
In this session Nicholas shares the techniques Twitter uses to hire amazing people, unleash their productivity, assess their performance, and improve the flock. Don't miss your chance to see how one of the fastest growing tech companies in Silicon Valley operates and retains the brightest talent.
Georgia Tech: Performance Engineering - Queuing Theory and Predictive ModelingBrian Wilson
This is one lecture in a semester long course \'CS4803EPR\' I put together and taught at Georgia Tech, entitled "Enterprise Computing Performance Engineering"
----
Performance Engineering Overview - Part 2…
Queuing Theory Overview
Early life-cycle performance modeling
Simple Distributed System Model
Sequence Diagrams
Collaborative Consulting provides software performance engineering services to help clients ensure system scalability, stability, and quality. Their services include advisory services to assess performance engineering maturity, application readiness assessments to evaluate performance risks, production performance rescues to quickly restore functionality during issues, and application performance management to proactively monitor systems. Collaborative uses a proprietary performance engineering methodology applied throughout the software development lifecycle. They have experience across industries including healthcare, financial services, and retail.
The Salesforce Platform allows developers to build enterprise applications using Visualforce, Apex and SOQL. To ensure that your applications perform and scale as your business grows, you'll want to write efficient and selective queries. The Force.com query optimizer uses several algorithms to determine the best SQL to generate from your SOQL. Some factors involved in this process include multitenancy, metadata and indexes.
Watch this webinar to:
Get an overview of multitenancy and metadata
Understand how to write selective and scalable SOQL queries
Learn how the Force.com query optimizer converts SOQL to SQL
See examples of the performance impact of indexes
Find out how skinny tables work
With every passing day, organizations are becoming more and more mindful about the performance of their Software Products. However, most of them still on look-out for the basics of Performance Engineering.
According to a recent study by Gartner, fixing performance defects near the end of the development cycle costs 50 to 100 times more than the cost required for fixing it during the early phase of development. Hence, if a product suffers from serious performance issues it can be completely scrapped.
Performance Engineering ensures that your application is performing as per expectations and the software is tested and tuned to meet specified or even the unstated performance requirements.
We present you with a webcast on Performance Engineering Basics that would walk you through the elements and process of performance engineering, and also offers a methodical process for the same.
It also offers details on a load testing tool, and describes how best to utilize it.
Visit http: http://www.impetus.com/featured_webcast?eventid=10 to listen to the entire webcast (20 minutes).
OR
To post any queries on Performance Engineering, write to us at isales@impetus.com
For case studies and articles on performance engineering please visit: http://www.impetus.com/plabs/casestudies?case_study=&pLabsClustering.pdf=
Effective performance engineering is a critical factor in delivering meaningful results. The implementation must be built into every aspect of the business, from IT and business management to internal and external customers and all other stakeholders. Convetit brought together ten experts in the field of performance engineering to delve into the trends and drivers that are defining the space. This Foresights discussion will directly influence Business and Technology Leaders that are looking to stay ahead of the challenges they face with delivering high performing systems to their end users, today and in the next 2-5 years.
An Introduction to Software Performance EngineeringCorrelsense
Software performance engineering is becoming increasingly important to businesses as they look to improve the non-functional performance of applications and get more out of IT investments. By leveraging performance engineering techniques, IT professionals can be indispensable in building and optimizing scalable systems. This
introductory course will teach you the essentials of software
performance engineering including :
• The performance challenges faced by Enterprise IT today
• What is software performance engineering (SPE)?
• Best practices for building scalable software systems
• The approaches to integrating SPE into IT project lifecycles
• Common frameworks for measuring application performance and service levels
• The impact of SPE on software developers, testers, capacity planes,
and other IT professionals
• Case studies from the finance, retail, and insurance industries
Instructor: Walter Kuketz, SVP and CTO, Collaborative Consulting
This training is sponsored by Correlsense, Collaborative Consulting,
and New Horizons
Have you ever been involved in developing a strategy for loading, extracting, and managing large amounts of data in salesforce.com? Join us to learn multiple solutions you can put in place to help alleviate large data volume concerns. Our architects will walk you through scenarios, solutions, and patterns you can implement to address large data volume issues.
Digital Team Structure: The Foundation for InnovationNTEN
The document summarizes research on digital teams at non-profit organizations. It finds that most digital teams are small (1-2 people), located in communications departments, and rely heavily on contractors. Top roles include social media, strategy, and content production. Teams manage many online properties and social media channels but lack necessary staffing and skills. While social media efforts are considered effective, digital programs overall are only somewhat effective and underfunded. However, most organizations plan to increase digital spending next year, indicating recognition of the importance of digital.
What team structure is right for DevOps to flourish? It is useful to characterise a small number of different models for team structures, some of which suit certain organisations better than others. By exploring the strengths and weaknesses of these team structures (or 'topologies'), we can identify the team structure which might work best for DevOps practices in our own organisations.
Update: see newer patterns at http://devopstopologies.com/ and the book Team Topologies at https://teamtopologies.com/book
This document discusses performance monitoring and testing in the Salesforce cloud. It describes how Salesforce uses a scalable, multi-tenant architecture to support over 60 billion transactions per quarter with an average response time of under 275ms. It also outlines how Salesforce's performance engineering team conducts internal testing to benchmark and monitor the platform, using both playback of production logs and synthetic workloads. The document provides guidance for customers on when and how to conduct their own performance tests, including identifying key transactions to test, using tools to capture metrics, and engaging Salesforce support for assistance.
Many companies are looking to move their CRM application from an on-premise to an on-demand environment. This webinar discusses the benefits and best practices of migrating from Siebel to Salesforce.com.
The document summarizes a presentation about analyzing e-commerce transaction data to identify related products for cross-selling recommendations. Some key points:
- Transaction data from Google Analytics can be analyzed in Excel and R to identify associations between frequently purchased product categories for cross-selling.
- Even basic cross-selling of clearly related products like baking tins with ovens can increase average order values and sales.
- Event tracking in Google Analytics can measure how often visitors use cross-selling tools on a site and how many of those visitors then make a purchase.
Agile-plus-DevOps Testing for Packaged ApplicationsWorksoft
Guest presenter Forrester VP and Principal Analyst Diego Lo Giudice joined Worksoft Agile expert Chris Kraus for an exploration of the state of adoption of Agile, DevOps and test automation in the enterprise packaged application space. Learn why it is important to include testing of packaged apps and mainframe as part of an Agile-plus-DevOps strategy and how the adoption of Agile and DevOps varies for packaged vs. custom-built applications. View the recorded event at: https://www.worksoft.com/downloads/worksoft-forrester-webinar-agile-plus-devops-testing-for-packaged-applications.
An overview of IT challenges and how Perficient China uses agile frameworks, methodologies, and practices to address these challenges and consistently deliver valued results to our clients.
This document discusses an agile development process used by Tech Propulsion Labs (TPL). It outlines key aspects of TPL's agile approach, including that it optimizes for flexible, business-driven projects and adapts to new insights. A major role discussed is the Product Owner, who acts as the customer representative and makes decisions for the development team. An optimal development path aims to get critical features launched quickly while deferring less important features.
In a DevOps environment, the DBA role is impacted and shifting. DBAs are now working on cross-functional teams that are responsible for the full software development lifecycle. They focus on areas like database provisioning for development, automating deployments, implementing monitoring and performance checks. This allows for faster code deployments and issue identification. The DBA role requires more technical skills like programming languages and automation tools to be successful in these DevOps teams and processes. Case studies show how DBAs have helped customers by automating deployments, implementing health checks and analytics to improve code quality and performance.
SharePoint: What You Need to Know Before UpgradingPerficient, Inc.
Perficient's Senior Architect Suzanne George outlines the key things you need to know before you upgrade your company's SharePoint implementation, including:
SharePoint terminology, features and versions
Roadmap planning
Licensing, upgrade and development tools
Undefined or forgotten costs
Requirements examples
Migration project plan
Governance
Content Migration Methodology
Upgrades
DF14-So Many Features Dreamforce ’14 Presentation FINAL-Monday-13OCT2014Mudit Agarwal
Our team introduced resources and programs to help customers drive adoption and ROI from Salesforce. The presentation discussed personalized success plans, success managers, success architects, and strategic projects from their certified Salesforce implementation team. It also covered training, certification, and customized learning paths to help customers get the most from their investment. Speakers from Dell and VMware then shared their journeys transforming with Salesforce and processes for evaluating new features in releases.
Many organizations engage in initiatives to develop elaborate reference architectures, patterns and governance processes in an attempt to optimize their enterprise. They put significant effort into the upfront guidance of development teams, and then find themselves challenged to understand how closely an architecture matches the approved approach after the projects complete. Organizations must take a new approach to this problem!
Transforming How We Deliver Value: Agility at ScaleTechWell
Continuous delivery in software development allows us to deliver incrementally, get quick feedback, and react. A key enabler is the adoption of agile techniques and methods; key inhibitors in the enterprise are size, scale, and complexity. The Rational ALM organization is a typical enterprise, and our teams have (mostly) adopted agile principles. But agility at enterprise scale is not the same as team-based agile development. Now we must coordinate work across multiple interdependent teams to deliver value, rather than focusing on developing a single product or application. Amy Silberbauer shares her experience of adapting SAFe in an enterprise organization and describes the struggles, mistakes, and successes throughout that process. Amy identifies the key challenges, including the need to identify value, provide the right data for various audiences, and the inherent required culture shift. Learn how to avoid some common pitfalls as you and your own organization embark on this same transformation.
Structuring the right team for DevOps without Re-Organization. I presented this at DevOps Fusion 2015. Tips include rapid feedback loop, value stream analysis, etc.
This document contains the resume of Amit Omprakash Dave, an IT professional with over 8 years of experience as a Senior Software Developer. It lists his contact information, objective of seeking a challenging position, technical skills including languages like Java and databases like Oracle, work experience with companies like Bank of America and JP Morgan Chase, and responsibilities held like coding, testing, and resolving issues. It also mentions certifications and achievements like securing the highest rating in assessments.
This document contains the resume of Abey Thomas which includes his contact information, objective, professional summary, education, certification and training, technical skills, functional skills, organizational experience and projects profile. The professional summary highlights his over 9 years of overall IT experience in software testing and development with specific experience in software testing, design and development. It also lists his expertise in various Oracle and PeopleSoft applications and tools.
The document provides a professional profile and summary for Sankaranarayanan G. It outlines his contact information, over 8 years of experience in business intelligence and reporting using tools like SAP Business Objects and Crystal Reports. It also details his experience with Oracle PL/SQL, Callidus incentive compensation management, and leading teams on various projects for clients like Citrix, Comcast, Comcel and Rogers.
The document discusses quality engineering (QE) and its role in a DevOps transformation at Salesforce. QE is involved at all stages of development to prevent issues. They work closely with developers, operations, security and other teams. The goal is to build quality into the product from the start and make quality everyone's responsibility, not just testing. A DevOps culture with strong QE collaboration can deliver high quality services to customers.
Take control of your Salesforce application with a governance process! Establishing a governance process helps us sort change requests and work with all of our stakeholders, from end users to developers. Join us as we teach you how to manage your entire application lifecycle process by instituting a governance process for your business.
Value Driven Development by Dave Thomas Naresh Jain
Agile, OOP... are like good hygiene in the kitchen, it results in meals with consistent quality and predictable prep and service times. It doesn't result in great meals nor substantially impact the ROI! Lean Thinking clearly shows that the only way to make a significant impact is to improve the value chain by improving flow. If everyone is following best practices no one has competitive advantage. Major improvements in the value chain depend on continued disruptive innovations. Innovations leverage people and their ideas. We use case studies to illustrate the different business and technical innovations and their impact. We conclude with a discussion of how to build and leverage an innovation culture versus a sprint death march when dealing with high value time to market projects.
More details: https://confengine.com/agile-india-2017/proposal/3608/value-driven-development-maximum-impact-maximum-speed
Habits of Highly Effective Platform Teams: Unlocking the Value of PCFVMware Tanzu
The key to truly being successful with Pivotal Cloud Foundry (PCF) is to have a dedicated team equipped with modern practices and methodologies running your cloud platform. Join Caleb and Parker from Pivotal Cloud Foundry’s Solutions team, as they discuss what a healthy platform capability looks like, and share practical advice on how to ensure your platform team is ready to unlock the full value of PCF.
This webinar is for all people who have purchased PCF and those that are considering doing so. In this webinar you will understand:
● What we mean by 'treat your platform as a product'
● The need for a dedicated platform team
● Why you need to adopt a culture of continuous improvement
● How to garner executive support in order to challenge convention
Presenters: Caleb Washburn, Director, Solutions Architect & Parker Fleming, Director, Solutions Architect, Pivotal
This document provides an overview of DevOps and how to adopt a DevOps approach. It discusses that DevOps aims to shorten the systems development life cycle and provide continuous delivery with high software quality. The document outlines that adopting DevOps involves changes to an organization's people, processes and technologies. It provides strategies for building a collaborative culture and implementing shared goals and metrics. It also discusses implementing efficient processes for continuous integration, delivery, testing and monitoring. The document recommends technologies like infrastructure as code, collaboration tools, and release automation to support the DevOps approach.
Org merges involve combining two Salesforce organizations into one. Key steps include setting up a project team, migrating business processes, metadata like profiles and custom fields, code including triggers and unit tests, and data. The Force.com Migration Tool allows migrating metadata between orgs using Ant scripts and the Metadata API. Project management is important to orchestrate the various migration tracks and deployment plan.
Manage Development in Your Org with Salesforce Governance FrameworkSalesforce Developers
As your team creates more apps in your Salesforce Org, you're faced with a new set of challenges: managing a well-designed org. Join us to learn about using the practices defined in the Salesforce Governance framework, and the set of tools available for managing issues such as security, coding standards, decisions over declarative verses Apex apps, design standards, overall Org strategy, and change control. By applying these best practices, your team can continue to grow your apps to meet the continuing challenges of your company.
Similar to How Salesforce built a Scalable, World-Class, Performance Engineering Team (20)
Sample Gallery: Reference Code and Best Practices for Salesforce DevelopersSalesforce Developers
This document provides an overview of the Salesforce Sample Gallery, which contains sample applications, reference code, and best practices for Salesforce developers. It describes different types of sample apps, including recipe style apps with specific code examples and standalone apps that demonstrate features. The document also outlines upcoming updates to the gallery, such as adding new applications and retiring outdated ones. It promotes benefits like inspiration, learning open source code, and understanding development best practices.
Maximizing Salesforce Lightning Experience and Lightning Component PerformanceSalesforce Developers
The document discusses various factors that affect the performance of Lightning Experience and Lightning Component pages. It outlines six main factors: geographical and network latency, device and browser capabilities, Salesforce org configuration, page complexity, component architecture, and server processing. For each factor, it provides recommendations for how to measure and optimize performance, such as enabling the Salesforce Edge network, limiting the number of components on a page, using conditional rendering, and leveraging caching features. The overall message is that page load time in Lightning Experience is sensitive to these infrastructure, code, and configuration factors.
Last year was eventful for Salesforce Developers - we started with the launch of Lightning Web Components (LWC), open-sourced it, enabled local development, and ended the year by open-sourcing Base Lightning Components. In this webinar, we will explore exciting new developments within Base Components and we will show you how to use open-source Base Components to build engaging applications faster with local development.
In this session we will,
- Spin up a local development environment to build Lightning web components
- Use and customize the base components and recipes to build pages and apps quickly
- Explore the latest features of VS Code developer tooling while coding for a use case
Over the past two months, we’ve announced many new resources for developers at Dreamforce and TrailheaDX India. To learn all about them, watch this video, where we'll explore live demos showcasing the latest updates for Lightning Web Components (LWC), Einstein, Heroku, and a lot more on the Customer 360 Platform.
In this session we,
- Explore key highlights from TrailheaDX India
- Show live demos of generally available features
- Explain how you can benefit from these features
TrailheaDX (TDX) is coming to ‘namma’ Bengaluru in India on Dec 19th and 20th! TrailheaDX India is the conference for everyone who builds on and customises Salesforce — including admins, developers, architects, and partners. This event will have sessions, demos and fun for those just getting started with the platform, as well as for advanced admins, architects and developers.
You might have questions about the event - and to answer your questions Kavindra Patel, known as the father of the Indian Salesforce Community, joins Shashank Srivatsavaya, Head of APAC Developer Relations. Register for our exclusive webinar to:
- Get a sneak peek into exclusive sessions and activities
- Find out who you shouldn’t miss at TrailheaDX India
- Understand what comes with your #TDX19 registration
CodeLive: Build Lightning Web Components faster with Local DevelopmentSalesforce Developers
GitHub repo: https://github.com/satyasekharcvb/lwc-local-dev.git
With the release of a new beta version of Local Development, you can now build Lightning web components faster than ever before! You can now render changes, iterate rapidly, troubleshoot errors, and even connect with data from your org by spinning up a local development server on your machine.
In this session, we build Lightning web components in real time. The exciting new capabilities we showcase will enable you to be an even more productive developer.
In this CodeLive session we:
- Spin up a local development server from the CLI to rapidly edit and view components
- Observe how a rich error handling experience simplifies testing and debugging
- Learn how to proxy data from an org for more context and fine-tuned development
CodeLive: Converting Aura Components to Lightning Web ComponentsSalesforce Developers
This document provides information about a Salesforce webinar on converting Aura components to Lightning Web Components (LWC). The webinar will feature two presenters demonstrating how to convert Aura components to LWC. The document includes forward-looking statements and disclaimers about product availability. It also provides information on asking questions during the webinar and resources for continuing the learning journey with Trailhead and the Trailblazer community.
Earlier this year, we released Lightning Web Components (LWC), a new UI framework based on web standards and optimized for performance and developer productivity. We have now open sourced the Lightning Web Components framework so that anyone can build applications on any platform.
Join our webinar where we'll explore how this framework, based on standard HTML, modern JavaScript (ES6+), and the best of native Web Components, helps you create web components and apps using the stack and tools you prefer.
We recently announced over 300 new features and enhancements at TrailheaDX '19 and for the Summer '19 release. In our Developer Highlights webinar we explore the top features with in-depth demos, including the latest updates for Lightning Web Components (LWC), LWC Open Source, CLI updates, Change Data Capture for external objects, Asynchronous Apex Triggers, Notification Builder and more.
Watch the recording here: https://youtu.be/kmOkk74QiCo
You can watch a recording of the live coding session at https://sforce.co/2IbU3yJ
In the fifth and final webinar of our five part series, we learn how to build Lightning web components for different use cases. We explore how to leverage all of the concepts you’ve learned in this webinar series to create modern apps with Lightning Web Components. We also demonstrate various ways to migrate Aura components to Lightning web components for a seamless transition.
This document discusses Lightning Web Components security and testing. It begins with forward-looking statements and risks related to new functionality, products, and services. It then provides information on debugging code, including using browser tools and debugging in different modes. Finally, it discusses unit testing Lightning Web Components with Jest, including prerequisites, configuration, and an example test file.
LWC Episode 3- Component Communication and Aura InteroperabilitySalesforce Developers
Lightning Web Components gives JavaScript developers a web standards-based path to building apps on the Salesforce Lightning Platform.
In the third episode of our five part series on Lightning Web Components, we cover design considerations and compositions of Lightning Web Components.
This document provides an overview of Lightning Web Components Episode 2 which focuses on working with Salesforce data. It discusses how the Lightning Data Service and UI API are used to retrieve and display Salesforce record data. It also demonstrates how to use wire services to connect Lightning Web Components to Apex methods to retrieve and manipulate data. The document concludes with instructions for configuring Lightning Web Components to be used in the Lightning App Builder.
Lightning Web Components are a JavaScript programming model for building web applications and interfaces that is built on the best of web standards.
Any front-end web developer can get started with LWC and leverage custom elements, and JavaScript APIs to create modern apps and experiences that are fully aware of Salesforce data and processes.
Migrate legacy Salesforce CPQ to Advanced Calculator with the help of JSQCP. With Advanced Calculator, you can boost the runtime of quote creation. Join this webinar to learn what is required for migration - we’ll also walk through JSQCP.
This document discusses techniques for addressing large data volumes (LDV) in Salesforce orgs, including big objects. Big objects are a special type of object designed to store and retrieve large data volumes using big data technology. The document also provides a use case where a company wants to archive closed cases to free up storage space while maintaining access. It recommends using a custom big object to address these needs. The webinar will demonstrate creating and deploying a custom big object and retrieving data using asynchronous SOQL.
Replicate Salesforce Data in Real Time with Change Data CaptureSalesforce Developers
Migrate your batch processing, scheduled ETL, and nightly workloads to event-driven, real-time integrations using Change Data Capture. CDC means data change events are published to an event stream, allowing businesses to have up-to-date information across systems and applications. Join us to learn how to configure Change Data Capture and subscribe to the stream of change events, streamlining your architectures and processes.
This document provides an overview of modern development with Salesforce DX. It discusses using source control and metadata with scratch orgs and the Salesforce CLI for source-driven development. Visual Studio Code is highlighted as an IDE for Salesforce development with features like the Salesforce extension pack. The document contrasts traditional org-based development with the new paradigm of package development where changes are tracked relative to package versions. It demonstrates these concepts with a live demo and encourages attendees to learn more on Trailhead.
Lightning Flow makes it easier for developers to build dynamic process-driven apps with Process Builder and the new Flow Builder. Join us and learn more about how you can get in the Flow!
Integrate CMS Content Into Lightning Communities with CMS ConnectSalesforce Developers
In this webinar we will show you how to display content from external Content Management Systems into Lightning Communities. This lets you take advantage of the Communities framework and help you centralize content in whatever CMS system you have chosen.
Integrate CMS Content Into Lightning Communities with CMS Connect
How Salesforce built a Scalable, World-Class, Performance Engineering Team
1. How Salesforce built a Scalable,
World-Class, Performance
Engineering Team
September 18th, 2012
Kasey Lee, Salesforce, VP Performance Engineering
in/leekasey
2. Safe Harbor
Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if
any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-
looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of
product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of
management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments
and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our
service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth,
interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other litigation, risks associated
with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain,
and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling
non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the
financial results of salesforce.com, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This
documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may
not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently
available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
4. A. I’m curious how PerfEng can excel in an Agile Environment
B. I’m curious how to utilize a Performance Engineer's time
C. I’d like to understand how to better articulate the value of
Performance Engineering
D. I thought this was a great place to take a break and check my
social feeds before dinner
E. A, B, or C
F. All of the above
5. What do typical Performance Teams start as?
“Performance Engineering is run as a Shared Services
model so your charter is the entire organization with
maximum visibility. Everything flows through PerfEng
because it’s so critical. Dev, QE, Technical
Operations, Level II and III Support, and Professional
Services wants the most out of your engineers by
leveraging your talent across projects to scale mission
critical applications”
8. Top Ten Signs Your Team Needs Help
1. You laugh when asked to signoff at Feature Freeze (and Release Freeze)
2. Your engineers work on 6-12 parallel projects (others work on 1-2 projects serially)
3. If you attended each of your assigned scrum teams’ daily 15 min standup you’d
never sit down (the entire week)
4. When you can’t signoff on a feature, everyone wants to raise the goals instead of
fixing the performance problem
5. Every day you answer “How did you decide to prioritize my feature? How can I
escalate this?” (even after you had agreement)
6. You’re told to commit to a plan for the next release while your team is busiest in the
current release and has no time to plan
7. Your team wants to influence the product or hardware architecture but can’t find the
time to even write up their analysis
8. Developers discount poor results due to variance without looking at the data (even
though the results of the latest release are always worse)
9. IT always asks “Why do you need isolated labs? Dev and QA don’t need them”
10.Devs ask your engineers to do manual tasks at all hours
10. What’s in store?
Introduction
The Unique Challenge at Salesforce
How the Team Scales
Workloads
Automation, Tools, Environments
Closing Thoughts and Tips
12. Brief Background
VP @ Salesforce
Performance Engineering
Sr. Director / Tech Lead @ Wily Technology
Performance Engineering, Software Tools, QA,
R&D Lab
Architect @ Event Zero
Developer, consultant for startups
Developer @ Ziff-Davis Benchmark Operation
Industry Standard Software Benchmarks
iBench, WebBench, ServerBench, NetBench
13. What drew me to Salesforce?
• Performance and Scalability is one of the
top three core values of the company
• One of the most complex Enterprise
scalability challenges anywhere
• As of today one of the best funded teams in
the industry and growing as quickly as we
can find the best people
14. What are some key challenges at Salesforce?
1. Mission Critical Enterprise Apps Customers pay for
No perf testing in production on unwary customers
No tolerance for downtime or slow response times which
immediately impact customers’ bottom line
2. Security is Paramount
Extremely difficult to access production systems / data
Can’t easily examine load and data shapes in detail
3. True Multi-Tennant Architecture
Every customer can create completely different load / data
characteristics at a moment’s notice
15. Noteworthy Milestones
Mid 2006 – “System Test” Team created from HA crisis
April 2008 – Kasey Lee joins a struggling team of 7
Sept 2008 – Automation & Tools Team Created
Sept 2009 – Team averts162 R1 Load Balancer Disaster
Jan 2010 – Leads solution to Capacity Planning crisis
Sept 2010 – Team predicts GC Heap 168 R1 Regression
Sept 2010 – Team leads solutions to NA6 Perf
Nov 2011 – Team helps reduce production CPU >60%
May 2012 – Team Triages 178 R1 Bytecode Regression
June 2012 – Team size rises to 60 Traffic & complexity
continues to increase to
Jan 2013 - Target size: 80+ ~60B / Quarter, but response
times have decreased!
16. Major Accomplishments ex. – “CPU 15”
• SWAT team optimization /
tuning efforts saved the
company ~$150 Million dollars
• Optimizations include potential
to change the JVM spec
directly to benefit everyone
• Great example of ROI
Not only in dollars, but helps
build the credibility that you can
leverage to do even more
19. How do we accomplish this?
• Baseline Functionality & Benchmarking
• New Feature Benchmarking
• Patches / Production Support
• Hardware / Infrastructure Analysis
• Special Studies / Research / POC
• Production Visualizations
• Capacity / Sizing Guides
• Architecture Expertise
• Profiling Concepts and Training
• Automation Frameworks
• Self Service Frameworks
• Data Analysis, Creation, Visualization Tools
• Load Generation Tools
• Environment Design
• Optimization
20. What We Continually Focus On
Blazing fast performance delivered by Cloud teams and PerfEng through
collaboration, innovation and transparency
Empowered and engaged PerfEng inspired by the real world impact of
their work and widely recognized as industry thought leaders
Quick and accurate test results, effective testing, seamless scheduling
and flexible environments
Frequent assessment, optimizations, and deep visibility into feature
performance during development and in production
Fully integrating PerfEng into product development as beneficial and
essential members of Cloud teams
Performance built in by Cloud teams and able to catch obvious
performance issues themselves
21. What really makes us so effective?
1. Our Perf/Dev ratios have been adopted (after numerous “discussions” )
2. We have a Software Development Team
3. We have a Product Owner (Prod. Mgr) for our Labs
4. We have a dedicated TechOps team “PerfInfra” for Labs
5. We have a substantial lab for testing
6. We have a Program Manager focused on cross functional project strategy,
visibility, and communications
22. Performance Engineering Team Structure
Performance Automation & Tools & Env
• Sales/Service/Data • Software Tools Developers
• Features • Environments
• Workloads • Product Owner
• Chatter • Special Projects Lead
• Features
• Workloads
• Platform/Mobile/UI
• Features Architect
• Workloads
• Core/Search/Analytics Program Manager
• Features
• Workloads
24. PerfEng Historical Lag per Release
Release R1
Planning Final Plans Due Feature Freeze Sandbox
Freeze
Product Development Sprints Release Sprint Release
Jan Feb Mar Apr May Jun
Accumulated performance bug debt
Cost of
finding &
fixing bugs
PerfEng Begins Testing
26. • Late starts with
minimal
workloads
• Increased
workloads and
decreased time
to bring online
• No longer need
to track
27. PerfEng Starts vs. Release Timeline
Release R1
Planning Final Plans Due Feature Freeze Sandbox
Freeze
Product Development Sprints Release Sprint Release
Jan Feb Mar Apr May Jun
28. Q: How do we do scale PerfEng to meet
demands of a larger organization?
29. Ratios are Key to Establish and Socialize
PerfEng established a 1:8 ratio of Perf/Dev IC
No more than two scrum teams or three projects / release
Does not include workload engineers (min of two per cloud)
Does not include Managers or Software Tools Engineers
Perf Managers/IC ratio may need to be higher than 1:8
Managers may require 1:3 or 1:5 due to the additional teams
managers interact with cross functionally
Find a ratio that enables PerfEng
Factor early participation, deep dives, optimization work to provide
meaningful contributions
Support discussion with velocity points, automation and efficiency
examples, ROI Examples
30. >1.2x
>2x
>2x
Gap is closing today, but still
haven’t reached the target
32. Embed Performance Mindset into Every Team
“Closely partner with scrum teams to
provide early, fast, continuous
architecture engagement / results /
analysis for complex scenarios and
enable scrum teams to catch obvious
performance issues with self service
tools, automation, and processes before
they reach Performance Engineering”
33. How We Interact with Scrum Teams
• Each scrum team appoints one Dev and QE engineer
who are mapped to a single PerfEng
• Teams must co-develop their release plans and sign off
criteria up front
• Teams are accountable for their features (complete
ownership coming back to PerfEng as team scales up)
• Teams must characterize obvious performance criteria
themselves every sprint (Cadence, PTest)
• Teams must deliver their features on time or accept
testing into the release sprint or beyond
35. Embedding Performance – A Tiered Approach
Increasing Test Complexity and Feature Risk
80% Scrum Team + 15% Scrum Team + 5% Scrum Team +
0% PerfEng 40% PerfEng 60% PerfEng
Single user transactions on Single user transactions on Corsa Single user transactions on IST
Desktops/Local Builds
Single user transactions in PTests High Load, High Concurrency on High Load, High Concurrency on
Corsa IST
Scrum Teams focus on catching obvious low-hanging
fruit; PerfEng focuses on difficult to construct, high
load/concurrency scenarios requiring highly specialized
knowledge to detect and analyze
36. 86 GB of meta data primarily from PerfEng workload tests!
37. 1.4 TB of meta data from tests created by Devs and outside teams!
38. Q: What are the key Agile Release
Milestones and activities for PerfEng?
39. Release Timeline and PerfEng Activities
Release R1
Planning Final Plans Due Feature Freeze Sandbox
Freeze
Product Development Sprints Release Sprint Release
Jan Feb Mar Apr May Jun
•Appoint Liaisons •Complete Release Plans •Double Check Exit •Initial visibility into •Signoff on all •Monitor Sandbox
Milestones
Criteria all features Features and •Final Optimizations
Workloads
•Signoff on ¾ of
features •Continue Workload
Optimizations
•Get workloads
green
40. How Do We Allocate Engineer’s Time?
70% Velocity Points Open
Feature or Workloads work for a specific cloud
30% Velocity Points Reserved
PTOn (9 days/year to work on whatever they want)
External Training Classes (e.g. SQL Tuning)
Other Cloud’s projects they are interested in
Conferences (e.g. HBase, Hadoop)
We Leverage Agile and
Foundation events (1:1:1) ADM to enable People’s
Changing Interests
41. Templates Cover Most Important Phases of a Project
Requirements/Arch Strategy/Test Plan Analysis/Results
42. Release Signoff Criteria and Team Dynamics
• PerfEng will only sign off on features we
worked on directly (or have thoroughly
reviewed the plans and results)
• Scrum Teams may sign off on features by
themselves at their own risk for any feature
with Medium or Less Risk (if PerfEng is
short of resources)
43. Quick Tip – Negotiating Release Criteria
Bring in teams from operations and support
Quote examples of consequences of releasing
without adequate throttles and caps in place
Cite examples from your company or other
leading companies of the cost of reduced
customer credibility
45. What is a “Workload”?
• A repeatable test simulation or benchmark that provides a
meaningful result by utilizing specific inputs into the system under
test while recording numerical metric data, which is subsequently
analyzed and weighted to perform a qualitative assessment
• Changing a variable in the workload and re-running provides a
meaningful comparison
• Baseline Workloads are automated and enhanced release over
release wherever possible
47. “Shape” Terminology
Load Shape – The distribution, rate, and
type of requests injected into the system
under test (SUT)
Data Shape - The size, skew, and type of
data, files, etc. accessed during the test
48. Categories
Playback tests take production traffic logs and replay traffic against the cut of data from
that time period
• This enables Salesforce.com to properly capture data skews, volumes, and transactions that customers have
run at a particular time and cover features that are heavily customizable
Synthetic tests involve utilizing custom tools to profile production load and data shapes
and then use custom tools to create workloads that mimic the desired characterisitics
• Synthetic tests enable the team to create data and load shapes that may be far greater or more accentuated
than in production, in a deterministic and precise fashion that enables granular studies of linearity,
bottlenecks, and resource utilization
• In most situations different versions of Salesforce are compared against one another, although absolute
performance metrics are used for new features or situations where it is too difficult to make meaningful
comparisons
49. Workload Highlights
Name Summary Load Shape Data Shape
DB Workloads A workload the replays real production requests against 100,000 complex Sanitized copy of real world production
customer data in a precise fashion to meticulously identify reports and filters Data with emphasis on massive data sets
proper DB stats, tuning for reports
Grinder A large scale, high load, high concurrency test that simulates an 400 RPS, target Sanitized copy of real world production
hour of peak production traffic by replaying transactions production Data
steady state
utilization of 35%,
peaks of 80%
Force.com Simulates traffic against a standard Ideas sites / base them Requests are Synthetic data based on real world force.com
application. generated across app “Ideas”
40 different URLs /
operations
Visual Force A read-only targeted test isolating specific components of VF at high 32 concurrent Small Synthetic VF classes. Viewstates,
request rates. Apex components are designed to be constant across requests across 10 Wrapperless / Wrapped nested data
all requests so regressions are to pure VF orgs presentation and Namespaces
Apex A targeted test that exercises the components of Apex Cache, CPU 64 threads across Synthetic set of classes that exercise Apex
consumption, Memory 16 organizations Cache, CPU Use of Apex L1, Maximal
number of lines of apex, creation of
temporary objects
Sharing A workload that performs DML Operations on Sharing Enabled Orgs, 2 app servers, 10 Synthetic Orgs (One Territory Managed,
Performs Sharing Rule Maintenance Operations on Various Entities, concurrent Users, One Regular)
Territory Management Operations and Accounts/Opportunity 7 Thread groups
50. Workload Highlights (continued)
Name Summary Load Shape Data Shape
Search High load, high concurrency test that simulates peak production traffic Replay production searches Sanitized copy of real world
by replaying searches and concurrently simulating incremental and performs incremental production Data
indexing. Monitors and reports metrics on entire stack [Indexers, DB, indexing at peak load. Issues
Query Servers, App Servers, Memcached] searches at 55 RPS
MQ Workload: A workload which enqueues messages into QPID on an IST using 20 app servers x 20 threads synthetic; configurable message
QPID multiple IST app servers. Tests QPID (the MQ transport service) in enqueue messages of size
(transport in isolation. Suitable for acceptance testing an upgrade. varying sizes for 10min-6hr
isolation)
MQ Workload: A workload which creates load on the integrated SFDC MQ framework 20 app servers x 20 threads synthetic; configurable message
Hydra using the SFDC MQ API library. Uses synthetic asynchronous handlers enqueue messages of size
(integrated) running on the app servers to simulate message and resource varying sizes for 10min-6hr
consumption. Suitable for running with every release, and for
simulating the impact of a new asynchronous handler.
Mobile Workloads simulate user actions over a real 3G network. Captures Real Device & Emulator. On Sanitized copy of real world
metrics to measure end-user perceived response times on slow Real 3G networks production Data
networks and real devices
UI Workloads simulate user actions in a real browser. Captures metrics to 6 Browsers – Nightly tests Synthetic user data – across all
measure end-user perceived response times. Org with Chatter data is standard pages. 3 Different orgs
very large. to test across different
skins/chatter.
51. Workload End to End Coverage* (At a Glance)
UI Network App Search Indexer FFX Batch DB SAN
DB Wkld 8 1
Grinder 1 8 3 3 3 3 7 3
Force.com 1 8 1
VF 7
Apex 7
Sharing 7 2
Search 6 6 6 4 3
MQ 6 2
Mobile 5 4 1
UI 8 5 4 1
Batch 6
*Higher numbers indicate better coverage in a given tier
52. Daily DB, Appserver, and UI Performance Tests!
Database Workloads
Appserver Workloads
UI - End User Response
Time Workloads
53. 168 – Performance Bugs ROI
Note that >50% of P0 bugs were
found by baseline workloads!
290 Total = 78 Workloads (27%), 211 Feature Testing (73%)
56. Michelangelo – Results Viewer
• Provides single point of
entry into all automated
tests
• Dynamic Test vs. Test
views
• Automatic Averaging of
test runs and filtering of
outliers
• Compare baseline to
results trends
57. Michelangelo Changelist Trend Example
• Dramatically shows
changes in performance
to the changelist
Specific
• Row and Column Changelist fix
highlighting results in 33%
more GC
• Color Coding activity
• Annotations
• Compare baseline to
results trends
• Absolute and Relative
difference comparisons
59. StatsForce – High Resolution
Time Correlated
Visualizations
Notice the
• OS Statistics benefits of
time
• Application Statistics correlation!
• JVM Statistics
• Errors Notice
how Full
GCs affect
• Mix and match Notice different
chart types Response
(scatter) on Times!
representations and chart same timeline!
types on demand
60. Statsforce Example - Force.com Workload Load
Balancer Regression
164 166
This looks odd!
64. Environment Types
Name Description Size
IST (Integration • Large scale pod. Closest to production in both software and hardware
System Testing) configuration (load balancers, 8 node RAC database, etc.)
• Primarily uses production data
CST (Comparison • Small environments focused on Database workloads
System Testing) • Primarily uses production data
DB Load (Prod, • Small environment with large sized DBs (4TB – 20TB)
Synthetic) • “Prod” uses production data , “Synthetic” uses synthetic data
Corsa (“Race”) • Small environments with hardware vertically identical to production
• Fewer horizontal nodes, focused on a particular SUT (Search, DB)
• Does not utilize production data
VMs / Autobuilds Dedicated environment for each engineer for development purposes
Desktops / Adhocs Dev local machines or Adhocs for PerfEng – dedicated for each
engineer for local tests or development
65. Continuous Data Refresh System
•Enables teams to access latest
production / synthetic data with
minimal downtime
•Performance tests can modify / delete
TB of data and rollback in minutes
Details
Production snapshots and corsa
images are taken periodically and
stored on SAN Refresh
A “jukebox” server prepares snaps
into “green” database images
The jukebox applies schema updates
and keep them “green”
The “green” images are always ready
to use and rsynched directly to the
environments
67. Where is Salesforce.com PerfEng Today? 30,000 ft. view
• Team has evolved from seven “Systest” engineers who
struggled to produce meaningful analysis, to a world class
Performance Engineering organization of >60 engineers with
no significant production issues the day after release for
almost three years
• Active participation in features, provides visibility and risk
assessment at critical milestones and averts major
degradations, helps triage and mitigate production issues,
delivers optimizations across the stack, and whose skills and
headcount are now lobbied for by Development teams
• Automation has increased from two workloads which ran a
handful of times late in the release, to over 15 sophisticated
workload suites that run every day and are critical to signoff
68. Top Ten Tips for Scaling Your Team
1.Socialize your ratios for PerfEng to Developers to eventually embed into teams
2.Propose a dedicated model over a shared service model
3.In a pinch, provide teams the velocity points they have funded, and ask them to prioritize
4.Build out your management team at every opportunity
5.Develop meaningful automated workloads with low variance and show the ROI regularly
6.Create a tools team that spends >=75% of their time developing automation and tools
7.Make your Labs and Test Frameworks self service
8.Develop production monitoring tools to collect relevant data for workloads and exit criteria
9.Create frameworks to enable staged work from Dev desktop to large scale Perf environments
10.Develop training classes for perfeng, new hires, Dev/QE liaisons – smaller population first
69. What else could be
responsible for this
dramatic optimization?
71. Bonus Tips for a Happy Team
• Contribute to a positive atmosphere that
promotes Autonomy, Mastery, and Purpose
with interesting projects to tackle in depth
• Focus on your strengths and strive to
improve at every opportunity
• Set a bold vision with achievable
milestones, and celebrate progress
72. What will you take from today?
What will you change starting next week?
“Is anything truly impossible? Perhaps it is
temporarily impractical or unlikely” – Kasey Lee
Ex. Human Exoskeletons (2:05)
75. Turn your PerfEng team from this… Into this…
Manual Black Box Testers Architecture / Analysis /
Simulation / Optimization /
Visualization / Automation /
Monitoring Experts
76. Lines of Defense
1. Single user requests in PTest on VMs
2. Single user requests / high load on Corsa
3. Concurrent / high load on Corsa
4. Single user requests on DB Load
5. Concurrent / high load on DB Load
6. Single user requests on IST
7. Concurrent / high load on IST