New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add hit/miss metrics for compiled code caches #7081
Comments
Merged this. |
Only ExpressionCompiler is implemented. |
Is anyone working on this issue? Otherwise I will go for it. |
@ebyhr Will you also handle JoinCompiler and JoinProbeCompiler classes, which require some refactoring? I was planning to work on those when I assigned this issue to myself (after I got no response to my ping), so I will be happy to take those if you don't have any plans, otherwise feel free to assign the issue to yourself. |
Sorry @nezihyigitbasi, I overlooked your ping. |
Now that #7333 is merged, closing this one. |
I suspect that the caches for compiled code are not very effective for large, varied workloads. We should add cache hit/miss metrics and expose them via JMX to be able to test this hypothesis.
Classes that need to be instrumented: ExpressionCompiler, JoinCompiler, JoinFilterFunctionCompiler, JoinProbeCompiler, OrderingCompiler
The text was updated successfully, but these errors were encountered: