Steps to replicate the issue (include links if applicable):
What happens?:
Notice that the cache-miss rate is above 2, that is above 200%!
What should have happened instead?:
It should be something that is actually possible.
Other information (browser name/version, screenshots, etc.):
This seems to be caused by the fact that for the last 3 years, we only track a sample of the lua events for performance reason, about 1 in every 1000 events. That was introduced in Add a sample rate for Lua function call tracking. That is achieved by comparing the sampling rate to a randomly generated number. However, the random number generator is never explicitly initialized and so every request gets the exact same list of random numbers!
In practice, this would sadly seem to mean that the Lua tracking data of the last 3 years is of questionably worth.