[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: newindex performance
- From: Gaspard Bucher <gaspard@...>
- Date: Sun, 19 Dec 2010 14:18:46 +0100
Thanks for the constructive comments Patrick and Steve. The
notification can be a (nearly) noop or a zeroMQ message sending so you
are right, performance is not an issue in the newindex part of the
system. My question was also on the pattern itself and apart from the
value change checking it seems ok.
This "property" pattern instead of a pipeline with inlets and outlets
is an important change for Rubyk and I felt a little unsure...
On Sun, Dec 19, 2010 at 10:34 AM, steve donovan
> On Sun, Dec 19, 2010 at 12:13 AM, Gaspard Bucher <email@example.com> wrote:
>> What is the performance impact of such an implementation ?
> Well, about the same as needing an explicit method/function. Also, the
> 'payload' of the operation (the on-change event) might be quite
> expensive (update a GUI, write to a log) so the performance loss would
> not be significant.
> BTW, probably better to only trigger on-change when the value actually changes.
> steve d.