Currently, the query cache uses the actual query as the key to the cache. This means bad things, when you’re using generated… was generated. What would work must better for the query cache key is simply a cryptographic digest of the tokens which the… a significantly higher hit rate and you don’t hit the query cache mutex lock so often because you only ever hit it when you…

… about keying off of *both* the actual query and a cryptographic digest of the tokens? I.e. attempt to hit the cache as… the digest. Upside: same cost in terms of parsing, higher hit rate. Downside: storing 2x keys, performing 2x lookups for true misses.