2016-08-30 11:12 GMT+02:00 Denis Kudriashov <dionisiydk@gmail.com>:

2016-08-30 10:35 GMT+02:00 Thierry Goubier <thierry.goubier@gmail.com>:

2016-08-30 10:28 GMT+02:00 Denis Kudriashov <dionisiydk@gmail.com>:

2016-08-30 10:21 GMT+02:00 Guille Polito <guillermopolito@gmail.com>:
Hi,

>From the top of my head: I would understand that systems where there are hundreds of thousands of events per second, maybe one does not want to pay the overhead of announcements...

But, How many events are produced from a morph per second? One? Two? Five? Is it really the case of morphs the one that require optimization?

I have similar feeling. But maybe Spec is nice example which could improved by such optimizations

No. Announcers are not the problem in Spec

I just saw that every property in Spec model's is kind of ValueHolder with announcer instance inside. And it is huge number. But I think in case of Spec they are always used. So laziness will not helps here. But optimisation for single subscriber could.

You're right. But I would consider making the value holder itself lazy (leaving it nil unless the model manipulates that property) so that you don't have to subscribe to a property which is never changed (and on the fly subscribe to it if it is lazily created by the model manipulation... could be a tad complex that one).

Thierry