Skip to content
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

dpnp.dot performance degradation by 4 times #1693

Closed
npolina4 opened this issue Feb 5, 2024 · 1 comment
Closed

dpnp.dot performance degradation by 4 times #1693

npolina4 opened this issue Feb 5, 2024 · 1 comment
Assignees

Comments

@npolina4
Copy link
Collaborator

npolina4 commented Feb 5, 2024

Performance degradation by 4 times for dpnp.dot function for current case.
Affected pairwise_distance workload

dpnp version #1669

In [1]: import dpnp
In [2]: a = dpnp.ones((21846, 3), device='cpu')
In [3]: b = dpnp.ones((21846, 3), device='cpu')
In [4]: c = dpnp.ones((21846, 21846), device='cpu')
In [5]: %timeit dpnp.dot(a, b.T, c)
1.18 s ± 59.2 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
In [1]: import numpy
In [2]: a_np = numpy.ones((21846, 3))
In [3]: b_np = numpy.ones((21846, 3))
In [4]: c_np = numpy.ones((21846, 21846))
In [5]: %timeit numpy.dot(a_np, b_np.T, c_np)
457 ms ± 9.27 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

dpnp version 0.13.1dev3+15

In [1]: import dpnp
In [2]: a = dpnp.ones((21846, 3), device='cpu')
In [3]: b = dpnp.ones((21846, 3), device='cpu')
In [4]: c = dpnp.ones((21846, 21846), device='cpu')
In [5]: %timeit dpnp.dot(a, b.T, c)
288 ms ± 12.1 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
@vtavana
Copy link
Collaborator

vtavana commented Feb 7, 2024

resolved in #1694

@vtavana vtavana closed this as completed Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants