No, it's not possible. These have not yet been implemented.
On Mon, Jul 15, 2013 at 4:19 PM, Tobias Bley t...@ultramixer.com wrote:
Is it possible to activate the optimizations for me in RoboVM 0.0.2 or
0.0.3 (github)?
Am 12.07.2013 um 17:11 schrieb Niklas Therning nik...@therning.org:
Hi Niklas,
thanks for your answer. I looked in the current code form github (RoboVM 0.0.3)
and found a „Level“ enum with -o3 optimization flag... so are you working on
the optimization support for LLVM?
Best,
Tobi
Am 16.07.2013 um 08:47 schrieb Niklas Therning nik...@therning.org:
No, it's
Is it possible to activate the optimizations for me in RoboVM 0.0.2 or 0.0.3
(github)?
Am 12.07.2013 um 17:11 schrieb Niklas Therning nik...@therning.org:
RoboVM doesn't do release builds yet (virtually none of LLVM's optimizations
are enabled) and virtual and interface method dispatch is
The performance is much better than JavaFX8 on iOS :(
Am 12.07.2013 um 15:37 schrieb August Lammersdorf, InteractiveMesh
s...@interactivemesh.com:
Found this on YouTube: http://www.youtube.com/watch?v=-scxqJjTJKI
August
That should be encouraging, since the CPU on the PI is *way* worse than the CPU
on an iPhone or iPad. Is the difference HotSpot vs. RoboVM? The graphics code
being executed should be pretty much exactly the same, and I would expect the
PowerVR to be able to handle this without any trouble.
BTW, we've run a VM performance benchmark against HotSpot on PI vs. RoboVM on
iOS and for raw power RoboVM seems faster (lower time to invoke a method, read
a field, etc etc). However in the real world RoboVM is slow and I don't know
why (GC overhead maybe)?
Richard
On Jul 12, 2013, at 7:52
I think these are the sample apps:
http://interactivemesh.org/testspace/j3dmeetsjfx.html
I take that back, the PI HotSpot numbers are generally faster than the RoboVM
iOS numbers (but RoboVM is faster than HotSpot when run as an interpreter,
obviously). We need to get our benchmark open source
Here's my acid test, put a square grid of circles in a scroll pane. Scale
up until pain is felt.
GridPane gp = new GridPane();
//int size = 3;
int size = 10;
//int size = 32;
// int size = 100;
//int size = 317;
for (int x = 0; x size; x++)
Have you tried running with the perf logger turned on? -Djavafx.pulseLogger=true
This will tell you a little something about where the time is spent. It might
not be detailed enough, but you can then put additional log statements in the
code to get more direct answers to questions about where
