And there is no "JVM slowness in general" for gene...
# tornadofx
e
And there is no "JVM slowness in general" for general applications, that's just at myth at this point ๐Ÿ™‚
โž• 4
๐Ÿ‘ 2
Haha, nice ๐Ÿ™‚
l
Thanks for your answers, though late. I talked about Java as slow because once I tried to adapt a C algorithm into Java, but Java general time to execute it was about 1 second to 2 seconds (which could be rather long for the user), while C took far less than one second.
It is the game "Le compte est bon", where one must reach a given number with 6 tiles number and the operations + - * /
But indeed, that the only case where I encountered such an issue.
e
@loloof64 When you say "time to execute" - do you mean startup time? That doesn't matter at all for a UI application.
l
No, it's not startup time, but the algorithm main computation time. Each time the 6 tiles and the target number were taken randomly, the program had to solve the "equation" : and that this solving process which was too long. So it's rather an event process.
e
OK. A JNI call might be the right thing to do in a situation like that though, unless there is something in the code that could be optimized for the JVM ๐Ÿ™‚
l
Yes you're right. JNI can be the solution : a little bit hard to learn (it's not the C side, I know it already), but this could ultimately be a solution. Thanks again ๐Ÿ™‚
Can make the work easier
e
It would be interesting to get a Java wizard to look at the code to see if it can be optimized further. Even SSL is pretty fast on the JVM these days, so there is hope ๐Ÿ™‚