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
Right now small tensors (in total entries and number of dimensions) appear to be faster in pyttb. However, for larger ones rusty_tensor (via PyO3 bindings) seems to win. We should figure out a range of sizes to compare against to look at the scaling trend. We should probably also investigate instrumenting rusty_tensor to see where we are spending the most time. I know we are doing a few unnecessary copies (at the rust/python boundary and at struct creation), but that might be a trivial amount of time for the scale of problems for now.
The text was updated successfully, but these errors were encountered:
ntjohnson1
changed the title
Generate Runtime Comparisons Across Tensor Sizes and Dimensions
Generate CP ALS Runtime Comparisons Across Tensor Sizes and Dimensions
Dec 30, 2023
Right now small tensors (in total entries and number of dimensions) appear to be faster in pyttb. However, for larger ones rusty_tensor (via PyO3 bindings) seems to win. We should figure out a range of sizes to compare against to look at the scaling trend. We should probably also investigate instrumenting rusty_tensor to see where we are spending the most time. I know we are doing a few unnecessary copies (at the rust/python boundary and at struct creation), but that might be a trivial amount of time for the scale of problems for now.
A couple unscientific comparisons on my machine:
The text was updated successfully, but these errors were encountered: