flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maximilian Michels <...@apache.org>
Subject Re: Improve performance of call system.currentTimeMillis()
Date Wed, 12 Aug 2015 12:39:12 GMT
I second Ufuk and Chensnay. Please provide us with a benchmark. I have a
hard time to believe your implementation, along with the overhead that
comes with it, will improve the streaming performance.

Please, feel free to prove us wrong :)

On Wed, Aug 12, 2015 at 11:48 AM, Chesnay Schepler <
chesnay.schepler@fu-berlin.de> wrote:

> -.-
>
> if you look at into this issue that you opened
> https://issues.apache.org/jira/browse/FLINK-2471 you were given opinions
> from 2 separate people, with arguments, that the performance
> improvement(TBD) is either a) nonexistant or b) negligible. All you did was
> disregard those basically saying "no I'm right.", and not much else. And
> now we're here starting at square one.
>
> SO, my suggestion is this: You said you could test the performance, so go
> ahead. Then we can talk.
>
> Regards,
> a slightly disgruntled Chesnay Schepler
>
>
> On 12.08.2015 11:33, Fangfengbin wrote:
>
>> Hello
>>
>>
>>
>> Some operators call system.currentTimeMillis() frequently and it is cost
>> performance.
>>
>> I want to use a thread to call System.currentTimeMillis and update a long
>> variable millTime. All other module do not need call
>> System.currentTimeMillis() and can get millTime directly.
>>
>> I want to know your suggestion. Thank you very much.
>>
>>
>>
>>
>>
>> Regards
>>
>> Fengbin Fang
>>
>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message