WIP: Shared arrays and GPU arrays #19
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces and extends #12
@dlfivefifty, I have some benchmark results for GPUs (K1000). I'll try and send a plot ASAP. The gist is that for relatively large blocks there is a speedup of ~4-5 compared to using a BlockArray backend. For similar matrices, there is also speedup of the BlockArray vs PseudoBlockArray backend (say of 1.x). Not sure whether it comes from the overhead from the Mul and friends setup, or whether it is tied to memory locality, or something else.
The shared array example works, though I have not benchmarked it yet.