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.

Sign up for GitHub

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

Jump to bottom

Thread scalable memory pool #212

Closed
ndellingwood opened this issue Mar 16, 2016 · 6 comments
Closed

Thread scalable memory pool #212

ndellingwood opened this issue Mar 16, 2016 · 6 comments
Assignees
@gmackey
Labels
Feature Request Create new capability; will potentially require voting
Projects
On-node Task DAG
Milestone
Spring 2016

Comments

@ndellingwood
Copy link
Contributor

Thread scalable memory pool for CPU and GPU.
Required by task policy and dynamically resizable view.
See issue #142 and issue #143
@ndellingwood ndellingwood added Feature Request Create new capability; will potentially require voting InDevelop labels Mar 16, 2016
@ndellingwood
Copy link
Contributor Author

More performant version under development.

@hcedwar hcedwar added this to the Spring 2016 milestone Mar 17, 2016
@crtrott
Copy link
Member

crtrott commented Apr 1, 2016

Can this be closed or is this undoing development?

@gmackey
Copy link
Contributor

gmackey commented Apr 1, 2016

There's a version in master that works, but it is not as thread scalable as we would like. I'm currently working on a new version that should be more scalable.

@gmackey
Copy link
Contributor

gmackey commented Apr 1, 2016

Forgot to say that this needs to remain open for now.

@hcedwar
Copy link
Contributor

hcedwar commented Apr 27, 2016

Current implementation has a race condition with extremely low probability, as exposed by very infrequent failures of the unit test. A new more performant and flexible implementation is in progress so this current race condition may not need to be addressed.

@hcedwar
Copy link
Contributor

hcedwar commented May 4, 2016 •
edited

New superblock based implementation is ~ 100x improved performance on GPU.
Need "get cycle register pull" on Power 8 for pseudo random number in search for available memory block. To be encapsulated in separate internal implementation.

@crtrott crtrott closed this as completed May 25, 2016
@hcedwar hcedwar added this to Backlog in On-node Task DAG Apr 19, 2017
@hcedwar hcedwar moved this from Feature Backlog to Done in On-node Task DAG Apr 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gmackey gmackey

Labels
Feature Request Create new capability; will potentially require voting
Projects
No open projects
On-node Task DAG
Done
Milestone
Spring 2016
Development

No branches or pull requests
4 participants
@hcedwar @crtrott @gmackey @ndellingwood