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

test cases and NEWS for #30372 (sparse matmul) #30433

Merged
merged 18 commits into from
Dec 20, 2018
Merged

test cases and NEWS for #30372 (sparse matmul) #30433

merged 18 commits into from
Dec 20, 2018

Conversation

KlausC
Copy link
Contributor

@KlausC KlausC commented Dec 18, 2018

#30372 needs some extra test cases to verify the implementation changes.

@ViralBShah
Copy link
Member

I would also mention the performance improvements for sparse matmul in the NEWS.

@ViralBShah ViralBShah added the domain:arrays:sparse Sparse arrays label Dec 18, 2018
@ViralBShah
Copy link
Member

Should we also add a'*b' for completeness to the tests?

Can we reduce the test cases to smaller matrices (not larger than 100x100) have just two: something with less than 1 nonzero per row/col on avg, and something that is several nonzeros per row/col. Too many tests here increases the testing time for everyone, and we need to be sensitive to that.

@ViralBShah ViralBShah changed the title test cases and NEWS for #30372 test cases and NEWS for #30372 (sparse matmul) Dec 18, 2018
@KlausC
Copy link
Contributor Author

KlausC commented Dec 18, 2018

Should we also add a'*b' for completeness to the tests?

I think, the as' * bs' tests the *(::Adjoint, ::Adjoint) case already.
I implemented your other hints.

@ViralBShah ViralBShah self-requested a review December 18, 2018 17:12
NEWS.md Outdated Show resolved Hide resolved
NEWS.md Outdated
#### SparseArrays

* `spmatmul` no longer has the obsolete optional keyword argument `sortindices` ([#30372]).
* performance improvements for `spmatmul` and hence for sparse matrix-matrix multiplication.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAICT we usually don't include things like this in news.

Copy link
Contributor Author

@KlausC KlausC Dec 19, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is a line like this ok or should I leave it out completely?

* performance improvements for sparse matrix-matrix multiplication ([#30372]).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fredrikekre Why do we not mention performance improvements in NEWS? That generally sounds like users would appreciate it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm just saying that we have not done it before.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Performance improvements can make the difference between usable and unusable in certain application scenarios. What do you recommend?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fredrikekre Fair enough. I think it is a good idea and I will merge it now. I also think that performance improvements are generally good to include across the board. If it is something we decide that we shouldn't do, we can always remove it.

NEWS.md Outdated Show resolved Hide resolved
stdlib/SparseArrays/test/sparse.jl Outdated Show resolved Hide resolved
stdlib/SparseArrays/test/sparse.jl Outdated Show resolved Hide resolved
@ViralBShah ViralBShah merged commit e7e33cc into JuliaLang:master Dec 20, 2018
@KlausC KlausC deleted the krc/spmatmatmul2 branch December 20, 2018 18:27
@ViralBShah
Copy link
Member

Do we add NEWS entries to the 1.0.x releases?

@StefanKarpinski StefanKarpinski added backport 1.1 status:triage This should be discussed on a triage call and removed backport 1.1 labels Jan 31, 2019
@Keno Keno removed the status:triage This should be discussed on a triage call label Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants