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

Potential performance improvement? #6

Closed
Staross opened this issue Feb 23, 2015 · 1 comment
Closed

Potential performance improvement? #6

Staross opened this issue Feb 23, 2015 · 1 comment

Comments

@Staross
Copy link

Staross commented Feb 23, 2015

Hi, I've been playing with TensorOperations and it seems pretty nice. I've noticed it's a bit slower (3-4x, Julia Version 0.4.0-dev+3052) than manual loops in some situations, probably because it allocates more memory. Maybe there's some potential to improve performances there:

http://pastebin.com/HkKU9fCp

@Jutho
Copy link
Owner

Jutho commented Feb 25, 2015

Well, there will always be many cases where manual loops for specific contractions are faster than the general purpose algorithm used by tensorcontract. It is impossible to have code that is optimal for any given contraction, unless one generates code for every given contraction. With stagedfunction in julia v0.4, this would in principle be possible, but given the exponential increase in possible number of contractions, this might not be feasible. It's something I would like to try out once I have some more time.

I will anyway be updating TensorOperations.jl to make use of some of the new features of julia v0.4 soon, and hopefully this will bring along some performance improvements.

@Jutho Jutho closed this as completed Apr 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants