Posted by Sven Gothel on Dec 18, 2014; 11:11pm
URL: https://forum.jogamp.org/NEWT-window-takes-10-sec-to-become-visible-on-multiple-monitor-setups-tp4033582p4033784.html

On 11/21/2014 02:47 PM, asambol [via jogamp] wrote:
> The profiler says the following 2 methods are the bottleneck:
>
> jogamp.newt.DefaultDumbassEDTUtil.invokeImpl() 3.198 ms
really? :)

Assuming you renamed that one for entertainment purposes? :)

Assuming this is just the caller for the function below?

> jogamp.newt.driver.windows.ScreenScrewYouDriver.getActiveMonitorName0[native]() 3.198
> ms

Well, I would recommend to analyze
the implementation of getActiveMonitorName0(), it is all there.

Note: We had a performance issue on some X11 RandR methods once
and analyzing each RandR method lead to the conclusion of caching some results.

Here, this is a new case, unknown to me. However, it will probably turn out
that some locking is the issue.


~Sven