3 ms·
Odds are the biggest bottlenecks in any webapp are going to be the DB and the network itself. So unless you're doing some really complex computations your actua
by imauld 10y ago
Odds are the biggest bottlenecks in any webapp are going to be the DB and the network itself. So unless you're doing some really complex computations your actual business logic likely won't be taking up most of the time between a request and a response. So you can work on something that will help you tune DB queries or you can take the DB out of (some) of the equation(s) and learn how to make good use of something like Redis or memcache to reduce DB load. Learn how to use a CDN to decrease static asset loading time.
I would also checkout this talk: https://vimeo.com/147806338 https://vimeo.com/147806338
It's pretty long but it's pretty funny and should give you some things to think about. There aren't any technical examples or demos but it's a good high level talk about the balloning size of web pages.