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

Move queues out of core #1

Closed
mrzv opened this issue May 23, 2015 · 2 comments
Closed

Move queues out of core #1

mrzv opened this issue May 23, 2015 · 2 comments
Assignees

Comments

@mrzv
Copy link
Member

mrzv commented May 23, 2015

Issue by Dmitriy Morozov
Friday Nov 14, 2014 at 17:51 GMT


Add the ability to move queues out of core (when their blocks are also out of core). For example, this is essential to support IO-efficient distribution of points (through a swap-reduce). Roughly, the protocol should be:

foreach block:
  process(block)
  exchange-light   # optional

exchange-heavy

exchange-light:
  post queues
  kick outstanding messages
  if #queues too large:
    swap some queues out

exchange-heavy:
  post any unposted queues   # happens if exchange-light wasn't invoked
  kick outstanding messages
  while there are external outgoing queues:
    if #posted queues < #allowed queues:
      load and post more queues
    kick outstanding messages

@mrzv mrzv self-assigned this May 23, 2015
@mrzv
Copy link
Member Author

mrzv commented May 23, 2015

Comment by Dmitriy Morozov
Wednesday Nov 26, 2014 at 21:35 GMT


This does not address what to do with incoming queues. These need more thought. Most likely, we have to re-engineer Communicator and Master. Specifically, Master might have to own incoming and outgoing queues and transparently to Communicator decide when they need to be moved in or out of core.

@mrzv
Copy link
Member Author

mrzv commented May 23, 2015

Comment by Dmitriy Morozov
Sunday Feb 08, 2015 at 21:30 GMT


Added loading/unloading of outgoing queues (fixes #1)

38f2975

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

1 participant