On Mon, Dec 22, 2014 at 2:41 PM, Wolfgang Friedl <
wolfgang.fri...@hotmail.com> wrote:
> Hi Endre!
>
> Thanks for the detailed description, this definitely helps.
> I'm looking forward for the final release.
>
You can still try the steps I recommended. When I say "not yet there" it
still means ab
Hi Endre!
Thanks for the detailed description, this definitely helps.
I'm looking forward for the final release.
Bester Regards
Wolfgang
Am Montag, 22. Dezember 2014 14:03:12 UTC+1 schrieb Akka Team:
>
> Hi Wolfgang,
>
>
> Well my real use case is a little bit more complex and correctly I do ha
Hi Wolfgang,
Well my real use case is a little bit more complex and correctly I do have
> some performance problems.
>
This would be probably not solved by a custom schedule at all. In fact
allowing custom schedules would completely deprive us from the flexibility
we need internally to do optimi
Hi Endre!
Well my real use case is a little bit more complex and correctly I do have
some performance problems.
I thought I could improve the performance by changing the relation between
Command (Request messages) and Data messages. So far this relation is 1:2
(at least this is what my tests a
Hi Wolfgang,
On Mon, Dec 22, 2014 at 1:10 PM, Wolfgang Friedl <
wolfgang.fri...@hotmail.com> wrote:
> Hi Endre!
>
> Thanks for the clarification, it does make sense :)
> Is it possible to define the "batching strategy" for simple operations
> like map? Or do I have to write a dedicated "processor
Hi Endre!
Thanks for the clarification, it does make sense :)
Is it possible to define the "batching strategy" for simple operations like
map? Or do I have to write a dedicated "processor" for handling this.
Wolfgang
Am Montag, 22. Dezember 2014 12:30:15 UTC+1 schrieb Akka Team:
>
> Hi Wolfgang
Hi Wolfgang,
What you see is completely expected. The strategy you added only defines
the strategy for that particular consumer. Once you attach other processing
steps, like those "map"s they do their own batching strategy independent
from what your consumer does. This is by design, backpressure s
Following Sample:
The "Producer" receives a different demand of elements dependent if the
flow does have processing steps or not.
(*Consumer uses the WatermarkStrategy(30)*)
var flow = Flow.empty[Int]
flow.runWith(PublisherSource(ActorPublisher[Int](intProducer)),SubscriberSink(ActorSubscr
