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

Possible optimization: central spike queueing #74

Open
stiber opened this issue Jul 17, 2014 · 2 comments
Open

Possible optimization: central spike queueing #74

stiber opened this issue Jul 17, 2014 · 2 comments
Assignees
Milestone

Comments

@stiber
Copy link
Contributor

stiber commented Jul 17, 2014

A central spike queue could mean that only those spikes scheduled for arrival get processed, rather than having to check for spike arrival at each synapse. Perhaps this could save a memory access or so for each synapse that doesn't have an arriving spike. In principle, it should save on the number of memory accesses needed to roll a queue forward for every synapse. It may also improve coalescing of some memory accesses. This is a non-trivial project; good for someone who is interested in going into the details of GPU performance and optimization.

photo

@stiber stiber added this to the Future milestone Jul 17, 2014
@stiber stiber modified the milestones: Future, Winter 2015 Nov 7, 2014
@stiber stiber modified the milestones: Winter 2015, Spring 2015 May 15, 2015
@stiber stiber modified the milestones: Spring 2015, Fall 2015 Oct 9, 2015
@stiber stiber modified the milestones: Fall 2015, Future Feb 21, 2016
@stiber
Copy link
Contributor Author

stiber commented Jul 20, 2016

Might be obsoleted by the forward map refactor

@stiber
Copy link
Contributor Author

stiber commented Mar 1, 2018

I'm pretty certain this is obsolete; @fumik , I leave it to you to decide to close this.

@stiber stiber removed the Multi-GPU label Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants