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

get multiple jobs per worker #235

Open
vkkhare opened this issue Jul 11, 2020 · 0 comments
Open

get multiple jobs per worker #235

vkkhare opened this issue Jul 11, 2020 · 0 comments
Assignees
Labels
Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint Severity: 4 - Low 😎 An aesthetic issue or is the result of non-conformance to a standard Status: Blocked ✖️ Cannot work on this because of some other incomplete work Type: Bug 🐛 Some functionality not working in the codebase as intended
Milestone

Comments

@vkkhare
Copy link
Member

vkkhare commented Jul 11, 2020

Description

PyGrid currently does not support multiple instances of jobs per worker mostly because it would need to have multiple socket connections per worker (one for each job). This can be solved when pygrid starts sending model name and version on cycle reject

@vkkhare vkkhare added Type: Bug 🐛 Some functionality not working in the codebase as intended Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint Severity: 4 - Low 😎 An aesthetic issue or is the result of non-conformance to a standard Status: Investigating 🔍 Something we are looking in to, but not currently in active development labels Jul 11, 2020
@vkkhare vkkhare added this to the 0.2.0 milestone Jul 11, 2020
@vkkhare vkkhare added this to To do in Model-centric Federated Learning via automation Jul 11, 2020
@cereallarceny cereallarceny moved this from To do to In progress in Model-centric Federated Learning Jul 21, 2020
@cereallarceny cereallarceny added Status: Blocked ✖️ Cannot work on this because of some other incomplete work and removed Status: Investigating 🔍 Something we are looking in to, but not currently in active development labels Aug 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint Severity: 4 - Low 😎 An aesthetic issue or is the result of non-conformance to a standard Status: Blocked ✖️ Cannot work on this because of some other incomplete work Type: Bug 🐛 Some functionality not working in the codebase as intended
Projects
Development

No branches or pull requests

2 participants