Hi Petr,
I was able to reproduce the problem. However, this issue has been fixed in our upcoming version. I tested the sample in our upcoming version and it took only 2 seconds. Here is the video clip for your reference:
Performance.zipOur next release (v5) is scheduled to be released within this week, which has great improvement in performance (reduced memory and better speed).
Kindly let me know if you have any other questions.
Regards,
Melba