There's a Time for Everything

on YouTube ↗55m

" summary

A retrospective case study of Banks.ru (a 10-year-old web portal handling about 2 million pageviews/day) examining when and how to optimize high-load systems. It discusses specific evolutions in architecture and technology choices, contrasts urgent fixes vs. gradual refactors, and argues that standard high-load best practices can sometimes be suboptimal for the business.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 1:42What We'll Talk About
3. 5:35Reactive Growth
4. 11:25Technological Solution
5. 12:25One of the Algorithms
6. 19:16Can We Find Patterns?
7. 24:02Premature Optimization
8. 25:19Component Optimization
9. 34:07Important to Remember
10. 47:25Cover Your Back

" related talks

• 42mTuning and Optimizing High-Load J2EE Web ApplicationsShamim Akhmed · HighLoad++ 2015
• 50mBuilding and Operating Online Shops under Extreme LoadPhilipp v. Criegern · code.talks 2017
• 36mMake It FastAlexander Solovyov · Highload fwdays'18
• 10mTechTalk "The Compromise Point Between Business and System Performance"Anton Abramov · HighLoad++ 2023
• 39mFrom Stubbies to LongnecksGeoffrey Giesemann · RubyConf AU 2013
• 56mLarge scale websites performance optimisation tricksGeorgiana Gligor · PHP UK Conference 2016
• 47mFrom Legacy to High-Load: Evolution of a Web ApplicationYevgen Lysenko · Highload fwdays'18
• 41mHigh Performance Kick-Ass Web AppsStoyan Stefanov · JSConf 2009