Hi Trambak.
The whole idea of Query Caching depends on your database engine. CMOD has no built-in functionality for that.
There are a few ways that data can be cached that aren't specific to CMOD though.
Inside DB2, there is a 'Query Optimizer' that spends CPU cycles trying to find the fastest way to service the query you're executing. The result of this optimization is cached. Therefore, if you run the same query again (even with different criteria) you'll get the quickest 'path' to the data, but without burning the CPU to determine that optimal path.
Also, if the 'second query' happens closely enough to the first, the database pages for the index and table might still be in memory, making it faster the second time, since the database wouldn't have to pull the pages from disk.
And finally, the operating system or disk storage subsystem may have additional caching that keeps recently accessed data in memory. This may also make a second query faster than the first.
However, with all of that being said, ALL queries should be coming back in a 0.1 seconds, or preferably less. If you aren't seeing this level of performance, you need to (in order of difficulty)... change your indexing parameters, tune your database, improve your I/O, or upgrade to new hardware.
Hope that helps!
-JD.
