Open elvin-n opened 1 year ago
Hey thanks for reporting! Would you mind elaborating what the M value is? Is it possible that it’s because the mixed usage of i32 and i64?
Would you mind elaborating what the M value is?
M is an input sequence length, for example. In case of dense it is batch size.
Is it possible that it’s because the mixed usage of i32 and i64?
Where dies it happen? If you refer to ForceNarrowIndexToInt32
transformation, then removing the transformation invocation does not affect behaviour
I found that tuning starts to work if I point seq_len = 32
. In opposite to unity where tuning starts to work if I point this parameter to 16
One more fact - Metascheduler worked for M == 32 with commit c0e455773792e0f551f3ad279ea39886fcc525ce but for the latest commit 5b8db51e5eb8a56d9e59f427c23b057119f59df0 it cannot tune for any size of M
Unable to tune linear/matmul having M value bigger than 1.
The error message is different comparing to Unity branch and this fact causes me to submit this bug, since changes in mlc-ai relax affected this use case and seems should be fixed here as well, not only in Unity