16. •Why server-side performance issues happen?
•Diagnosing and Solving
•Common Performance Issues
•Deep Dive into Cache Stampedes
Saturday, September 13, 14
17. Data...
URL where the issue happened? front-end? backend? both?
specific actions? Any errors seen or reported? Screenshot
or screencast available? Happening to everyone or just one
person or a small group? Happening everywhere (desktop,
mobile with 3G, mobile with wifi)? Reproducible
consistently? or Sporadic? etc...
Saturday, September 13, 14
18. Three RRRules to Make
Things Faster...
★ Reduce: Do fewer things
★ Reuse: Cache the things you already did
★ Recycle: Use existing code to do the
things
Saturday, September 13, 14
19. Free Bonus Rule
•Remove: Get rid of it completely...
Saturday, September 13, 14
I’m Scott Dadich the editor of WIRED. We could not be more thrilled at the prospect of partnering with USC for this incredible educational startup.
For more than 20 years we’ve been producing content for millions of readers and viewers, and the chance to engage in a deeper way with USC graduate students is an XXXXXX opportunity.
We hope you join us in thinking that our hands-on experience covering the latest in businesses, technology, and design will be a valuable addition to USC’s formidable academic reputation.
I’d like to take just a few minutes to talk about what we bring to the table.
Our archive is deep and rich and includes the WIRED take on almost every significant event in technology and business since 1993
Server-side PerformanceOutlineWhy server-side performance issues happen?Diagnosing and SolvingCommon Performance IssuesDeep Dive into Cache StampedesServers have finite resourcesAt any given point in time, webservers, database servers, and the like have limits to what they can support.Every extra millisecond spent in a calculation or a functions or a query is a lost millsecond for someone else.