Sometimes the problem is not that a query is expensive, but that it seems to execute too frequently, more than what it should need to, and then the combined execution cost, for both the JVM and the DB, becomes significant. In this post I wanted to discuss this scenario and how caching can be used to reduce the executions.
Queries executing is not necessarily a problem. WebSphere Commerce needs the database to store and query data, so you will see queries. The problem is when the number of executions is unreasonably large... [Continue Reading]