Web Developers often fixate on optimizing the delivery of assets to the end-user’s device, and overlook the computation that takes place on the end-user’s device once those assets arrive. By Joe Liccini.
Further reading in the article:
- The importance of asset delivery
- Web application bottlenecks
- A concrete scenario
- System overview
- IPC cost
- Disk cost
- Parse and compilation cost
Inter-Process Communication (IPC) is how processes in the browser send messages between each other.
Browser cache stores cached files on the end-user’s device on disk. Disk access is not granted to the process executing your web application and is performed by the dedicated Network process, which loads cached assets from disk for all tabs and windows across the browser. Caching assets is a fantastic way to optimize the network overhead of your web application, there is still plenty of computational overhead associated with cached JavaScript. Good read!
[Read More]