3 ms·
No matter how slow the frontend is, the quicker the execution of that script finishes, the quicker that process can handle another request, saving you resources
by pilif 15y ago
No matter how slow the frontend is, the quicker the execution of that script finishes, the quicker that process can handle another request, saving you resources.
- rimantas 15y agoProperly optimized front-end will help your servers a lot. Case of typical website: 6-15 JavaScript files, handful of CSS files, tens of images, 60-100 HTTP requests. On repeat visit still the same amount of requests, majority of them are just 304 Not Modified Case of FE optimized website: 1 request for main document, one for combined and minimized .js, one for combined and compacted .css, 1-4 for CSS sprites files and some content images. Repeated request: 1 request for document (the rest of resources have far future expire time so are not requested). Server has to serve order of magnitude fewer requests.
- pilif 15y agoAgreed, but all the static assets shouldn't be served by your application server but either from a completely different machine (or CDN), or at least from a reverse proxy in front of the application server. Aside of eventual port or file handle starvation, serving assets should have no effect on your application server. So while having one file with all the assets is advantageous for the end users, it should have no or next to no influence on application server performance.