Hi Fabian
Thank you, yes there are just map functions, i will do it that way with
methods to get it faster
On Fri, Aug 10, 2018, 5:58 AM Fabian Hueske wrote:
> Hi,
>
> Elias and Paul have good points.
> I think the performance degradation is mostly to the lack of function
> chaining in the
Hi,
Elias and Paul have good points.
I think the performance degradation is mostly to the lack of function
chaining in the rebalance case.
If all steps are just map functions, they can be chained in the
no-rebalance case.
That means, records are passed via function calls.
If you add rebalancing,
Hi Antonio,
AFAIK, there are two reasons for this:
1. Rebalancing itself brings latency because it takes time to redistribute the
elements.
2. Rebalancing also messes up the order in the Kafka topic partitions, and
often makes a event-time window wait longer to trigger in case you’re using
Hello
Sending ~450 elements per second ( the values are in milliseconds start to
end)
I went from:
with Rebalance
*++*
*| **AVGWINDOW ** |*
*++*
*| *32131.0853 * |*
*++*
to this without rebalance
*++*
*| **AVGWINDOW ** |*
*++*
What do you consider a lot of latency? The rebalance will require
serializing / deserializing the data as it gets distributed. Depending on
the complexity of your records and the efficiency of your serializers, that
could have a significant impact on your performance.
On Thu, Aug 9, 2018 at
