FamilySearch improves application performance while increasing load and data—without adding any new infrastructure—using AppDynamics.
FamilySearch International, a non-profit organization sponsored by The Church of Jesus Christ of Latter-day Saints, is the world's largest genealogy organization.
Millions of people worldwide rely on FamilySearch to preserve and provide free access to genealogical records of every kind.
With more than 10 petabytes of data, the FamilySearch service was a challenge to manage, especially as it grew. “We're growing the system at an incredibly fast pace of 300 million new records per year and 300 million new images,” said Bob Hartley, Principal Engineer and Development Manager at FamilySearch. “We're on the path to 20 petabytes of data, and more.”
FamilySearch started out with an Oracle database, Java and Enterprise JavaBeans (EJB) to power its search engine, but quickly found that this architecture could not support the data. “The amount of time it took to query the database against 3 billion records to return one record was just completely unacceptable to users,” Hartley said. “They don't want to wait minutes.” FamilySearch quickly realized that simply scaling infrastructure was not an efficient way to manage performance and would be prohibitively expensive. They needed to find a way to maximize application performance while the load and data grew exponentially.
“Adding more infrastructure would have been very expensive for us—it would have cost us millions in hardware, power and administration costs. The fact that we've avoided having to do that has been huge for us.” Hartley and his team estimated that the deferred hardware costs amount to nearly $3.5 million in savings for FamilySearch.
A year after first implementing the AppDynamics solution, Hartley and his team reviewed their progress and found that throughput increased from 11,500 transactions per minute to 122,000 transactions per minute. In addition, Hartley and his team reduced the response time of their longest-running transactions. We've taken the mean-time-to-recovery for our problems from days down to a matter of minutes.
Hartley found that by giving his team access to AppDynamics, they were able to more quickly respond to performance issues that arose in the application. “We've taken the mean-time-to-recovery for our problems from days down to a matter of minutes,” said Hartley. “
We estimate we've saved about $460,000 in productivity costs alone, just by reducing the amount of time we all spend troubleshooting issues.”