You could set up a system where the workers in the cluster send IPC messages for the key that they're interested in, and the master can send a response.
However, you'd probably be better off just using a database like Redis for this. It's very fast, and will allow you to scale to multiple machines/zones quite easily. On Sun, Sep 16, 2012 at 5:17 AM, karl <[email protected]> wrote: > Hi, > I have a large read-only data set which I'd prefer not to load into each > worker (for memory reasons). Instead, I was thinking of loading it in the > master and using the communication channels to have the master return > results to the worker processes. > > To scale, I was thinking the master could launch threads via TAGG (or > something), which, as I understand it, share the same memory as their > creator. > > Sound good? > > Karl > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
