ement, which happens to be 100ms by
>>>>> default. You can decrease this value to some extend, at to cost of
>>>>> potential loss in throughput, but I think even values around 5-10ms are
>>>>> ok-ish. See [1] for more details. If you want t
;>>
>>> Best,
>>> Stefan
>>>
>>>> Am 20.09.2018 um 16:03 schrieb James Yu >>> <mailto:cyu...@gmail.com>>:
>>>>
>>>> The previous email seems unable to display embedded images, let me put on
>>&g
gt; <mailto:cyu...@gmail.com>>:
>>>
>>> The previous email seems unable to display embedded images, let me put on
>>> the links.
>>> Hi,
>>>
>>> My team and I try to measure total time spent on our flink job and found
>>>
gt;> My team and I try to measure total time spent on our flink job and found
>> out that Flink takes 40ms ~ 100ms to proceed from one operator to another.
>> I wonder how can we reduce this transition time.
>>
>> Following DAG represents our job:
>>
> http
;> The previous email seems unable to display embedded images, let me put on
>> the links.
>> Hi,
>>
>> My team and I try to measure total time spent on our flink job and found out
>> that Flink takes 40ms ~ 100ms to proceed from one operator to another. I
>
et me put on the
> links.
> Hi,
>
> My team and I try to measure total time spent on our flink job and found out
> that Flink takes 40ms ~ 100ms to proceed from one operator to another. I
> wonder how can we reduce this transition time.
>
> Following DAG represents ou
The previous email seems unable to display embedded images, let me put on
the links.
> Hi,
>
> My team and I try to measure total time spent on our flink job and found
> out that Flink takes 40ms ~ 100ms to proceed from one operator to another.
> I wonder how can we reduce this
Hi,
My team and I try to measure total time spent on our flink job and found
out that Flink takes 40ms ~ 100ms to proceed from one operator to another.
I wonder how can we reduce this transition time.
Following DAG represents our job:
and here is the screenshot of our log:
at 19:37:04.564
