Reducing CPU Cycles and RAM Size
There is always a trade-off between the speed of an application and its size. Repeatedly retrieving data creates a cost in speed to yield a decrease in size. Stored and reused data increases speed but creates a cost in increased size. The best solution depends on the situation. Wasting either memory or time is always a bad choice. If speed is of the essence and memory is cheap, then follow a design that favors data caching. If memory is a limitation, then favor the opposite design. In most cases a hybrid of the two approaches is needed to get the best results in any given application. Some data or functionality must be reused continually and so should be retained in memory. Other data or functionality is used ...
Get Oracle Database Ajax & PHP Web Application Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
