This is a simple strategy applicable when it is acceptable to show dirty data at times and also the data in the database does not change very frequently. Timed cache strategy where the cache can be replenished periodically (i.e. ![]() You could say that one of the two following strategies can be used: Data can be eagerly loaded with a help of SQL scripts with complex joins or stored procedures and cached using third party frameworks or building your own framework. need to make several database calls) where eagerly loading data and caching can improve performance by minimizing network trips to the database. load only when required as opposed to pre-loading from the database with a view that it can be used later) from a database to conserve memory but there are use cases (i.e. In general data should be lazily loaded (i.e. Database calls are remote calls over the network. Most applications need to retrieve data from and save/update data into one or more databases. Remote method invocations involve a network round-trip, marshaling and unmarshaling of parameters, which can cause huge performance problems if the remote interface is poorly designed. Minimize network overheads by retrieving several related items simultaneously in one remote invocation if possible.switching between threads as opposed to doing real computation.). Having too many threads in a pool also can result in performance and scalability problems due to consumption of memory stacks and CPU context switching (i.e. Optimize the pool sizes based on system and application specifications and requirements. Also consider using multi-threading in your single-threaded applications where possible to enhance performance. Creating new threads and discarding them after use can adversely affect performance. Emphasize on reuse of threads from a pool of threads. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |