On 11.09.2018 08:04, Stephan Knauss wrote:
The AWT Eventqueue looks a bit generic. YourKit can point to "Long AWT
Events" in the "Threads" tab. I have for example one longer than 5s.
I stored a snapshot here. Can't shorten the timeline I think, but
resetting telemetry caused only the last "long event" of 8s having call
stacks I think.
http://downloads.osm-tools.org/josm-custom-2018-09-11(7).zip
I don't understand why the events tab does not have call stacks recorded.
It seemed that whenever I did not use JOSM for a few minutes because I
scrolled around in the profiler or source and then go back to JOSM and
zoom I got a wait. One time over 22 seconds.
Can someone more familiar with the profiler confirm that the AWT loop is
not blocked but simply busy for that long?
Is it filling tasks to JCSCachedTileLoder.submit()?
I don't know how to limit the CPU analysis to that timeframe to see
where the cycles go.
Stephan
