You will need to build OpenJFX from source to get the windows
implementation of the ES2 pipeline. We strip it out of jfxrt.jar before
shipping it.
-- Kevin
Tobias Bley wrote:
Hi Jim,
that’s very interesting. BTW: Where do I get the ES2 implementation for Windows?
I will remove all extern d
I just tried this app on my MacBook Pro (Retina, 15-inch, Mid 2015)
The framerate was always 60fps. The higher performance AMD graphics processor
was active - as it is for all Java programs :-(.
The CPU usage reported for the process by Activity Monitor varied between 18
and 30%, and settled at j
Hi,
currently our experiences with JavaFX on Mac are very disappointing. While
JavaFX on Windows runs very good with low cpu usage, JavaFX on Mac via Java 8
doesn’t perform well. I created a little clock app which uses between 25% and
80% cpu usage. But what’s the reason for? I though JavaFX r
Hi,
I recently updated the project on github
(https://github.com/tobium/JavaFXPerformanceTest). I removed the dependencies
and added several new tests, e.g. JavaFX using Canvas and Swing tests.
All of these tests perform well (1% CPU) on Windows, all of these tests doesn’t
perform well on Mac
Hi Jim,
that’s very interesting. BTW: Where do I get the ES2 implementation for Windows?
I will remove all extern dependencies in the the project.
Best regards,
Tobi
> Am 10.07.2015 um 02:19 schrieb Jim Graham :
>
> I was able to verify the CPU usage on my retina MBP and further show that ES
Hi Jörg,
Java Swing performs much better on Windows using D3D than on Mac using
OpenGL/Quartz…. so I suppose the OpenGL implementation on Mac isn’t very
good….maybe that’s the reason for the new Metal rendering API on Mac 10.11?
Best regards,
Tobi
> Am 10.07.2015 um 00:21 schrieb Jörg Wille :
I was able to verify the CPU usage on my retina MBP and further show
that ES2 on Windows also consumes a similar amount of CPU:
Mac (using ES2): 20-25%
Windows (using D3D): 3%
Windows (using ES2): 20%
so this is definitely related to our use of OpenGL and not a Mac
platform issue (though it di
Hi Tobi,
I have ran your clock app on an old
MacBook Pro (15 Zoll, Late 2008) (2,4 GHz Intel Core 2 Duo)
NVIDIA GeForce 9400M 256 MB
Mac OS X 10.10.4
JDK 1.8.0_45-b14
using:
java -Dprism.verbose=true -jar javafx-performance-test-1.0.0.jar
which shows that the GPU pipeline is used.
Loading ES2 nat
Hi Jim,
please checkout the small app on Github:
https://github.com/tobium/JavaFXPerformanceTest
Mac OS X: 10.10.4
Mac Book Pro Retina (Late 2012), Intel HD Graphics 4000 1024 MB, 8 GB RAM, i7
2,6Ghz
Java FX 1.8.0_60
FPS: Mac and Windows: 60 FPS
CPU usage: Mac: 25-80%, Windows: 0-3%
Best re
Hi Tobi,
Can you share your small clock app? Perhaps file a bug and attach the
source?
Also, what version of MacOS are you running on what hardware? (And
compared to what version of Windows on what hardware?)
...jim
On 7/7/15 4:32 AM, Tobias Bley wrote:
Hi,
cu
On Tue, Jul 7, 2015 at 1:32 PM, Tobias Bley wrote:
>
>
> Hi,
>
> currently our experiences with JavaFX on Mac are very disappointing. While
> JavaFX on Windows runs very good with low cpu usage, JavaFX on Mac via
> Java 8 doesn’t perform well. I created a little clock app which uses
> between 25%
Hi,
currently our experiences with JavaFX on Mac are very disappointing. While
JavaFX on Windows runs very good with low cpu usage, JavaFX on Mac via Java 8
doesn’t perform well. I created a little clock app which uses between 25% and
80% cpu usage. But what’s the reason for? I though JavaFX
12 matches
Mail list logo