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
[AutoTVM] AutoTVM incorrect measurement #5215
Comments
@FrozenGene what is the status of this issue? |
This issue wants to track all template of using |
@FrozenGene In #5200 we discussed another source of autotvm inaccurate measurement due to empty input tensor. Do we have a timeline to fix that? |
I hope we could bring this with Auto Scheduler this month if every thing goes well. |
@kevinthesun FYI. We are rebasing our code based on the laster master. After completing it, this fix will be brought in. |
@FrozenGene please update the status of this issue |
ping @FrozenGene |
Currently, as listed, we have completed |
OK, we will leave the issue open then, please remember to update it as we add more improvements. |
@FrozenGene please check if we can close this issue either due to non-actionable status(stale) or completion |
i think we could close it as Ansor solves the problem for all platforms. For AutoTVM's cuda platform, there is no activity on it. If anyone is interested on it, he / she could do it for cuda on AutoTVM too. |
Our AutoTVM use
debug_skip_region
to skip our precompute stage (like precompute kernel). However,debug_skip_region
can not reflect practical running, which just only create empty tensor for it. Empty tensor will make AutoTVM record the performance incorrect. This condition will become worse like Winograd. In Winograd, our weight shape will be changed from (KH, KW, CO, CI) to (alpha, alpha, CO, CI). Alpha equals totile_size + KH - 1
. If tile_size is 4 (KH is 3), then alpha is 6. So to avoid this issue, we should avoid usingdebug_skip_region
in all platforms of AutoTVM template and use the technique like this PR: #5200.Open this issue to track this.
The text was updated successfully, but these errors were encountered: