Reminder, Monday is our weekly sanity testing.
You can find your testing assignment at:
https://wiki.openjdk.java.net/display/OpenJFX/Sanity+Testing
Please note that assignments were changed.
Also please remember that the repo will be locked from 1am PST until 1pm
PST.
Happy testing!
Thanks,
Sorry, take 2.
Thanks - that's very helpful.
I have been concentrating on profiling the Java aspects of FXMark so this gives
me more things to try.
I will report back with my findings.
Blessings,
Felix
> On 22 Jul 2016, at 19:02, Vadim Pakhnushev
> wrote:
>
>> On 22.07.2016 11:15, Felix B
> On 22 Jul 2016, at 19:02, Vadim Pakhnushev
> wrote:
>
>> On 22.07.2016 11:15, Felix Bembrick wrote:
>> Hi Vadim,
>>
>> I am very open-minded about this. Anything is possible (including, as I
>> mentioned, that I wrote FXMark very poorly).
>>
>> Can you help by detailing what tools you use
On 22.07.2016 11:15, Felix Bembrick wrote:
Hi Vadim,
I am very open-minded about this. Anything is possible (including, as I
mentioned, that I wrote FXMark very poorly).
Can you help by detailing what tools you use to track CPU/GPU usage?
I personally use Process Hacker (I'm on Windows) and
Hi Vadim,
I am very open-minded about this. Anything is possible (including, as I
mentioned, that I wrote FXMark very poorly).
Can you help by detailing what tools you use to track CPU/GPU usage?
I am sure finding out the exact nature of what is happening and what is causing
it will help every
Felix,
For me it's very useful to track CPU/GPU usage while running a benchmark.
Could it be that your very fast machine is limited by some
synchronization issues and CPU/GPU is essentially idle while slower
machine is running 100% CPU?
Vadim
On 22.07.2016 3:35, Felix Bembrick wrote:
I am w
