Re: Methods that trigger execution

2017-06-07 Thread Aljoscha Krettek
Hi, I’m afraid I don’t know that part well enough. What’s the percentage in slowdown? (7 seconds alone doesn’t say anything) Maybe Till (in cc) knows more since he used to work on the ML part. Best, Aljoscha > On 6. Jun 2017, at 17:45, Borja wrote: > > *Thank so much Aljoscha* :) > I was stu

Re: Methods that trigger execution

2017-06-06 Thread Borja
*Thank so much Aljoscha* :) I was stucked in this point. I didn't know that the print or collect method collecting all the data in one place. The execution time has dropped a lot. However, I still get that Flink is slower (just for 7 seconds). I really think I'm not getting all the performance ou

Re: Methods that trigger execution

2017-06-06 Thread Aljoscha Krettek
Hi, Using collect() (or print()) on a DataSet is almost never a good idea in Flink because this requires collecting all the data in one central place and sending it to the client. What you normally would do is write the data out to some file system (for example HDFS) and use env.execute() for a

Re: Methods that trigger execution

2017-06-05 Thread Borja
Hello, I just reading about this, because I am developing my degree final project about how performance spark and flink. I've developed a machine learning algorithm, and I want to trigger the execution in Flink. When I do it with my code it takes around 5 minutes (all this time just in the collect

Re: Methods that trigger execution

2017-05-03 Thread Aljoscha Krettek
Hi, Yes you’re right, there is no convenient list. Off the top of my head, your list seems exhaustive. (You could add printToErr()). As a general remark, I don’t think it’s wise to use these methods when handling large amounts of data because they ship everything back to the client. Best, Aljos