The current SEND implementation is probably not as fast as a plain CALL, since send must create a new thread of execution. On the other hand, it's almost certainly fast enough that this won't be where your bottleneck proves to be.
> I was doing a bit of a thought experiment considering how I would design
> a particular app to run on eros, and I have a question about the cost of
> the SEND call.
>
> In this hypothetical program, there are a number of domains (most likely
> small domains), all of which contain no thread. However, on occasion, an
> event is triggered, and one of these domains would require a thread in
> order to perform an operation on its data in response to the event.
>
> Since there would be a controlling domain, I thought that the
> controlling domain could simply use the SEND call to create a thread in
> the domain which requires servicing. But, is using the send call
> expensive? Or is it as cheap as a plain CALL? I ask this simply because
> the program's performance is a quite important goal in its design.
>
> thanks, theApe
>
>