#18075 closed defect (worksforme)
JOSM slow with MapCSS on openSUSE systems
Reported by: | stoecker | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core mappaint | Version: | |
Keywords: | performance | Cc: | Don-vip, Klumbumbus |
Description (last modified by )
Hello,
today I did a bit of maxspeed mapping and used the maxspeed style.
As soon as following rule kicked in, JOSM became awfull slow:
/* 6.3 - report conditional maxspeed without default maxspeed */ way["maxspeed:conditional"][!"maxspeed"]::maxspeedlayer, way["maxspeed:forward:conditional"][!"maxspeed:forward"][!"maxspeed"]::maxspeedcasinglayer, way["maxspeed:backward:conditional"][!"maxspeed:backward"][!"maxspeed"]::maxspeedcasinglayer { color: yellow; dashes-background-color: red; dashes: 4,24; opacity: 1; width: 5; text: tr("conditional maxspeed without default maxspeed!"); text-color: black; font-size: 11; text-halo-color: red; text-halo-radius: 2; left-casing-width: 1; left-casing-color: yellow; right-casing-width: 1; right-casing-color: yellow; left-casing-opacity: 1; right-casing-opacity: 1; z-index: 1; }
It seems the text rendering is causing an extreme slowdown. For some time now JOSM seems slow to me on openSUSE systems, but I couldn't nail down the reason. As far as I can see it independent from the java version, but for reference here is what I used (recent openSUSE Tumbleweed).
openjdk version "1.8.0_212" OpenJDK Runtime Environment (IcedTea 3.12.0) (build 1.8.0_212-b4 suse-2.2-x86_64) OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
To be able to use josm at all I disabled display of most area styles.
I'd appreciate if someone with a bit more skills in timing debugging could test openSUSE. If this is not a generic JOSM issue (which I don't believe, otherwise there would be much more complains) it must have a reason in something different in modern openSUSE distributions.
Attachments (0)
Change History (6)
comment:1 by , 6 years ago
Component: | Core → Core mappaint |
---|---|
Description: | modified (diff) |
Keywords: | performance added |
comment:2 by , 6 years ago
comment:3 by , 6 years ago
Also, please try with Java 11. Java 2D rendering has completely changed in Java 9.
comment:4 by , 6 years ago
Last time I tried it did not help, but you're right. With java 11 JOSM is as smooth as I know it. Now I have a java11/8 mixup, as the compilers still need to be 8 for compatibility :-)
comment:5 by , 6 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I'll think about a way to ensure that java > 8 is used for the JOSM opensuse package.
comment:6 by , 6 years ago
JOSM is now started with this commandline. This uses default java except lower than 11. In this case it tries java 11 if existing.
LIBXCB_ALLOW_SLOPPY_LOCK=1 `perl -e '$res = "/usr/lib64/jvm/jre-11-openjdk/bin/java"; $res = "java" if !-f $res || qx(java -version 2>&1) !~ /version \"(\d+)/ || $1 >= 11; print $res'` -Xms64M -Xmx1024M -XX:+UseParallelGC -XX:+UseAdaptiveSizePolicy -jar /usr/share/java/josm-tested.jar "$@"
What happens if you remove the text-halo properties?