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

Vectorized decompression #38

Merged
merged 18 commits into from
Aug 1, 2019
Merged

Vectorized decompression #38

merged 18 commits into from
Aug 1, 2019

Conversation

ChrisRackauckas
Copy link
Member

It is slower but potentially useful for GPUs:

# Vectorized: 13.366 μs (16 allocations: 5.08 KiB)
# Loop: 2.513 μs (4 allocations: 2.41 KiB)

@matbesancon
Copy link
Contributor

can't we specialize for GPU and keep the looping default?

@ChrisRackauckas
Copy link
Member Author

Yes, this is just prototyping. I wrote this on a plane and pushed it so we wouldn't lose what the correct translation is, because it's pretty gnarly. I may finish it up later or if @pkj-m has a GPU and wants to try pushing the GPU algorithm until CuArrays.allowscalar(false) works he can.

struct ContractionColor <: ColoringAlgorithm end
struct GreedyStar1Color <: ColoringAlgorithm end
struct GreedyStar2Color <: ColoringAlgorithm end
abstract type SparseDiffToolsColoringAlgorithm <: ArrayInterface.ColoringAlgorithm end
Copy link
Contributor

Choose a reason for hiding this comment

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

SparseDiffToolsColoringAlgorithm not a fan of the package name plugged into types, C-like. Couldn't we not-export ColoringAlgorithm, thus calling it with SparseDiffToolsColoringAlgorithm. Other solution would be to remove the abstract type all together and use ArrayInterface.ColoringAlgorithm directly

test/test_ad.jl Outdated Show resolved Hide resolved
ChrisRackauckas and others added 2 commits July 30, 2019 09:54
Co-Authored-By: Mathieu Besançon <mathieu.besancon@gmail.com>
@ChrisRackauckas ChrisRackauckas merged commit 923f8a8 into master Aug 1, 2019
@ChrisRackauckas ChrisRackauckas deleted the vectorized branch August 1, 2019 01:49
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

Successfully merging this pull request may close these issues.

3 participants