Re: mirage + froc = self-scaling?

[Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>]

On 28 Mar 2013, at 11:36, Anil Madhavapeddy wrote:

> to help nail the semantics down.  Each Froc cycle should spin up a new process
> that runs its own Lwt thread, with explicit handoff between them for 
> resources.

just trying to understand what you mean by this. i have to this point been 
looking at having a Froc graph constructed from multiple cells (a tuple of 
Changeable and setter function), and then having each Lwt thread capture one of 
the setters so that it can push a new value into the Froc graph in response to 
external IO. the bit i'm finding mildly tricky at the moment (or was until 
today, which is mostly being about annual performance reviews :/ is managing 
the Lwt thread pool correctly. (ie., calling Lwt_main.run on the right things.)

(a) does this sound sane or am i missing the point?

(b) are you suggesting that each time an input comes in on an Lwt thread i 
should spin off a new process and explicitly hand off resources, in order to be 
completely clear what and where are the resources?  (primarily IO handles and 
such like i guess?)


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may 
contain confidential information. If you have received this message in error, 
please send it back to me, and immediately delete it.   Please do not use, copy 
or disclose the information contained in this message or in any attachment.  
Any views or opinions expressed by the author of this email do not necessarily 
reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.