-
Notifications
You must be signed in to change notification settings - Fork 796
[SYCL] optimize enqueueImpKernel by making trace faster #20682
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
base: sycl
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -222,8 +222,7 @@ class PersistentDeviceCodeCache { | |
|
|
||
| /* Sends message to std:cerr stream when SYCL_CACHE_TRACE environemnt is set*/ | ||
| static void trace(const std::string &msg, const std::string &path = "") { | ||
| static const bool traceEnabled = | ||
| SYCLConfig<SYCL_CACHE_TRACE>::isTraceDiskCache(); | ||
| static const bool traceEnabled = SYCLConfigTrace::isTraceDiskCache(); | ||
|
||
| if (traceEnabled) { | ||
| auto outputPath = path; | ||
| std::replace(outputPath.begin(), outputPath.end(), '\\', '/'); | ||
|
|
@@ -232,8 +231,7 @@ class PersistentDeviceCodeCache { | |
| } | ||
| static void trace_KernelCompiler(const std::string &msg, | ||
| const std::string &path = "") { | ||
| static const bool traceEnabled = | ||
| SYCLConfig<SYCL_CACHE_TRACE>::isTraceKernelCompiler(); | ||
| static const bool traceEnabled = SYCLConfigTrace::isTraceKernelCompiler(); | ||
| if (traceEnabled) { | ||
| auto outputPath = path; | ||
| std::replace(outputPath.begin(), outputPath.end(), '\\', '/'); | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I understand, the main point of optimization is that you removed from the hot path the check if traces are enabled because you changed the reset logic. But why did you replace the template specialization with a new
SYCLConfigTraceclass? Why not apply this optimization to theSYCLConfigtemplate class, so that it is enabled for all configs?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have seen only this one having impact on flamegraphs. You are righ - it is worth to look at other ones and try to unify approach. Changing pattern for others may be a next step. I just wanted to save time now and focus on hunting next perf bottlenecks.
SYCLConfig template class was already specialized for traces. It does not use common code from SYCLConfig. Maybe it is possible to unify this code also for all other config values. Maybe it is not - for some reason we had this specialization. I did not analyzed the rest of variables deeply.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It sounds like you suggest accumulating the tech debt in favor of performance.
So, since we already achieved the initial perf targets the pressure from our customers is decreased, so we should look for clean solution instead of intermediate steps.
In that particular case, what was the reason to get rid of template specialization?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not introduce tech debt. I do not optimize all the code. Just the most important one. I don't do premature optimization.
Because this particular template specialization is useless. The simpler code, the better. A class without a template is simpler than templated class.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is exactly my concern: this PR introduces a discrepancy. So far, we have a unified design (maybe not the best) with template specializations for a particular config. Now we have a dedicated class (perhaps it is a simpler approach and more readable) for a particular config.
I agree that we should not do premature optimizations. But in that particular case I just suggest that we need to unify the design for all config types.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can change all specialization to concrete classes. I like simplifying the code. Will that be OK for now?