@ffbin: Would this be a JVM singleton that updates a static field every millisecond?
It is hard to say at this point whether this eliminates a bottleneck, but I think it is fine to try. To evaluate this, you could use a streaming job that attaches a timestamp to every record, and measure the different throughput with and without this service. I curious what the results are! On Wed, Aug 12, 2015 at 2:39 PM, Maximilian Michels <m...@apache.org> wrote: > 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.schep...@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 > >> > >> > >> > >> > > >
