I’ve been reading about the SQL Query Result Cache. This is where actual query results are cached so that the query doesn’t need to be run again unless something in the tables has been changed. It could be thought of conceptually as creating an on-the-fly materialized view for that specific query. I was planning a post about it when I saw several others have already done very thorough write-ups:
The upshot is that it’s a nifty new feature and the problem with the single latch in 11GR1 appears to be solved, but it needs to be heavily load tested before trying it in a production environment.