Today, profiled search requests are eligible for request caching, which can lead to some very confusing situations (fast took time but slow profile results because the results are being served by the cache). Profiling should never really be cached at all because of the nature of profiling.

Related, ProfileWeight delegates isCacheable() to the wrapped query, but I wonder if we should perhaps return false to prevent the profiled query from affecting Lucene's caching statistics?