arrayfire / arrayfire/arrayfire-dotnet
Execution time speed compared to ArrayFire C++
- Langage dominant
- C#
- Étoiles
- 76
- Forks
- 19
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Hi,
I have developed a Arrayfire image processing algorithm in C++. The execution time was around 78-80 ms. Then, I re-implemented the algorithm via the .NET wrapper. Now the execution time is around 120 ms. Is it normal?
PS: I also noticed the .net wrapper leverage 50 of the GPU however the original one used 100 percents
One more thing, the .net wrapped version has no "warm up" time however the original C++ version needs about 1 min to execute for the first time. I am not sure yet if its normal or not!
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start by comparing the C++ and .NET implementations described in the issue, including their execution times, GPU utilization, and first-run behavior. Done means determining whether the reported differences are expected or identifying a reproducible wrapper performance problem; the payload names no files or tests.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- cpp, csharp
- Domaine
- performance
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100