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

Allow task scheduler memory pool to be used by tasks #747

Closed
hcedwar opened this issue Apr 25, 2017 · 0 comments
Closed

Allow task scheduler memory pool to be used by tasks #747

hcedwar opened this issue Apr 25, 2017 · 0 comments
Assignees
@hcedwar
Labels
Enhancement Improve existing capability; will potentially require voting
Projects
On-node Task DAG
Milestone
2017-July-end

Comments

@hcedwar
Copy link
Contributor

hcedwar commented Apr 25, 2017 •
edited

The incomplete matrix factorization task-dag algorithm needs dynamically allocated scratch space that persists across tasks but does not persist beyond the task-dag. Allowing the task scheduler's memory pool to be used by the tasks would satisfy this requirement. The factorization algorithm must estimate the total memory required for scratch space plus "live" tasks when constructing the task scheduler and its memory pool.
@kyungjoo-kim
@hcedwar hcedwar added the Enhancement Improve existing capability; will potentially require voting label Apr 25, 2017
@hcedwar hcedwar added this to the 2017-June-end milestone Apr 25, 2017
@hcedwar hcedwar self-assigned this Apr 25, 2017
@hcedwar hcedwar added this to In Progress in On-node Task DAG Apr 26, 2017
hcedwar added a commit that referenced this issue Apr 27, 2017
@hcedwar
Allow a TaskScheduler to accept a memory pool and expose
4499c8f 
the memory pool that it uses.  issue #747
@hcedwar hcedwar moved this from In Progress to In Develop in On-node Task DAG May 12, 2017
@crtrott crtrott closed this as completed May 27, 2017
@hcedwar hcedwar moved this from In Develop to Done in On-node Task DAG Jun 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hcedwar hcedwar

Labels
Enhancement Improve existing capability; will potentially require voting
Projects
No open projects
On-node Task DAG
Done
Milestone
2017-July-end
Development

No branches or pull requests
2 participants
@hcedwar @crtrott