I'm doing some database benchmarking in Python using the cx_Oracle module. To benchmark results, I'm running 150 unique queries and timing the execution of each one. I'm running something like this:
c = connection.cursor()
starttime = time.time()
c.execute('SELECT /*+ NOCACHE */ COUNT (*) AS ROWCOUNT FROM (' + sql + ')')
endtime = time.time()
runtime = endtime - starttime
Each query is passed in through the variable sql
, and they vary significantly in length, runtime, and the tables they access. That being said, all queries exhibit the following behavior:
1st run: very slow (relatively)
2nd run: significantly faster (takes anywhere from 1/2 - 1/5 the time)
3rd run: marginally faster than 2nd run
All subsequent runs >= 4: approximately equal to 3rd run
I need the cache disabled to get accurate results, but the first few runs are really throwing off my data; it's as if NOCACHE
isn't working at all... what's going on here?
Edit: Allan answered my question, but for anyone who might be interested, I did a little more research and came across these two pages which were also helpful:
How to clear all cached items in Oracle
http://www.dba-oracle.com/t_flush_buffer_cache.htm
Oracle recommends using the CACHE setting to enhance performance if you are using sequences in a Real Application Clusters environment. Specify NOCACHE to indicate that values of the sequence are not preallocated. If you omit both CACHE and NOCACHE , the database caches 20 sequence numbers by default.
Caching of data for better performance has been the goal of the Oracle architecture for a very long time. When a query is executed for the very first time, the user's process searches for the data in the database buffer cache.
The FLUSH SHAREDPOOL clause is useful if you need to measure the performance of rewritten queries or a suite of queries from identical starting points. Use the following statement to flush the buffer cache. SQL> ALTER SYSTEM FLUSH BUFFER_CACHE; System altered.
USE_NL. The USE_NL hint causes Oracle to join each specified table to another row source with a nested loops join, using the specified table as the inner table.
From the documentation:
The NOCACHE hint specifies that the blocks retrieved for the table are placed at the least recently used end of the LRU list in the buffer cache when a full table scan is performed. This is the normal behavior of blocks in the buffer cache.
It seems from this that the nocache
hint simply doesn't do what you expect it to.
You can clear the shared cache by running ALTER SYSTEM FLUSH SHARED_POOL
and the buffer cache by running ALTER SYSTEM FLUSH BUFFER_CACHE
. You'll need to do this between each query to prevent the cache from being used.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With