You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
I have a problem is that when I do the dnn predict, where I will use the SyncCopyFromCPU and the Forward, the batch_size and fea_num is 40,default blas is openblas(I have also tried the Intel mkl,but it doesn't work),the cpu is broadwell,58 logical core total。
I have 32-58 worker thread,each thead only have 1 openmp thread,I worry that open too many openmp thread will decrease the performance。
After the test, I found that , the predict totally cost 13.9ms, SyncCopyFromCPU cost 275us, but the Forward cost 11ms, have can i reduce the forward cost time ?
I have a problem is that when I do the dnn predict, where I will use the SyncCopyFromCPU and the Forward, the batch_size and fea_num is 40,default blas is openblas(I have also tried the Intel mkl,but it doesn't work),the cpu is broadwell,58 logical core total。
I have 32-58 worker thread,each thead only have 1 openmp thread,I worry that open too many openmp thread will decrease the performance。
After the test, I found that , the predict totally cost 13.9ms, SyncCopyFromCPU cost 275us, but the Forward cost 11ms, have can i reduce the forward cost time ?
The text was updated successfully, but these errors were encountered: