GPU Prototype #94
Closed
GPU Prototype #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey! I thought it's about time to do some GPU experiments. I have working protoype for that in
GPU_network.jl.Since our whole GraphStructure/GraphData business is really complicated to bring to the GPU memory I went for a quit different approach implementing a toymodel first. The main idea is to split the network in homogeneous parts (as with the old network layer stuff or more recently in #91 ). Once we have homogeneous subsystems, maybe we don't need a lot of the complex structure anymore.
Thats why i decided to build a minimal working prototype first which only works for homogeneous systems. This mini example supports both, CPU and GPU. I compared all calculations against NetworkDyanamics. Here are some benchmarks for the coreloop:
And some benchmarks for a solver run with
Tsit5()(around 260 timesteps).As of now the prototype can't handle autodiff, thats why i've choosen the explicit solver...