I recently bought a chromebook with an ARM processor (the Asus Flip). I'm using Crouton to run the xfce in a chroot, to provide a full (lightweight) Linux desktop. Everything is working great, except JOSM. It is painfully laggy, with multiple second delays for every action. Click on menu, wait 2-3 sec for it to open. Click on node, wait 1-2 sec for to to be selected. Zoom, wait 4-8 seconds. Pretty much unusable. I bought this laptop for an upcoming bicycle trip, that I am planing to do lots of mapping with it. Because I specifically bought this laptop for running JOSM it's unusability is quite disappointing. I'm running JOSM from the latest tested .jar file from the command line, giving it extra RAM, with the -Xmx2048m option. The version in the Ubuntu repositories is very old, so I'm not using that (the building plug-in is not supported!). The bottleneck might be the CPU. It's Rockchip 1.8GHz Quad-core. Sounds fast to me, but htop reports one of the cores in the mid 90 percent range when zooming, or after downloading fresh data. They remain low at other times, despite lag with other tasks. RAM usage always remains low. Is there a way to optimize CPU usage? Looking at htop, I seem to have multiple threads running. Sorry if my question is too specific to my needs, I can make it more applicable to others by asking: How do I trouble shoot JOSM lag, and optimize performance to mitigate lag? Update: I've added Sun/Oracle Java, as per the info from aseerel4c26 and rorym and JOSM is now running very responsively. I'm really happy with the results. asked 09 Aug '16, 20:52 keithonearth aseerel4c26 ♦ |
What java are you using? I found the open source java to be very very slow for JOSM and noticed a massive speed in JOSM when I switched to the closed source Sun/Oracle java. answered 10 Aug '16, 09:39 rorym 1
when I type:
it outputs:
(10 Aug '16, 10:09)
keithonearth
That looks like the open source Java. The logo used when JOSM starts will also tell you. I suggest installing, and switching to, the closed source java, it might be much faster.
(10 Aug '16, 10:10)
rorym
1
@keithonearth: try to update to Java 8. You are running version 7. The next JOSM "tested" release (in a few days) will not run with this old Java version anymore. Small performance improvements are expected, too. For comparison, this is an example
(10 Aug '16, 13:01)
aseerel4c26 ♦
|
It seems (see "Update" below) there is no openJDK VM for ARM processors available which uses (fast) assembler code. See http://icedtea.classpath.org/wiki/ZeroSharkFaq "As an interpreter-only port of OpenJDK, Zero is very much slower than vanilla OpenJDK on the same hardware." You seem to run "Zero VM" (see your java version output). Slowness of all Java applications is expected – but at least they run (that's the goal of "Zero"). Other Java applications should run comparatively slow, too. Update: according to Wikipedia, openJDK looks to be available also without "Zero" for ARM. answered 10 Aug '16, 13:02 aseerel4c26 ♦ Thank you! Installing Sun/Oracle Java has improved the performance so that it's faster than on my x86 laptop. It's working beautifully now.
(10 Aug '16, 19:44)
keithonearth
@keithonearth: fine! :-) Could you please provide the
(11 Aug '16, 00:28)
aseerel4c26 ♦
|
Sounds more like a bug or incompatibility. Did you already test if the problem persists when using different JOSM versions (stable vs latest), a different JRE (openjdk vs Oracle JDK) or another window manager?
BTW: There are some reports that Asus Flip runs apps from Google Play store as well. Did you try e.g. Vespucci?
Also tried JOSM on my Raspberry PI 2 (also some ARM chipset) using Oracle JDK 8 via remote ssh session. Although it's a bit sluggish it's not completely unusable, running even on 0.9GHz CPU speed only, though. Oracle JDK can be installed via
sudo apt-get install oracle-java8-jdk
on Raspbian.@mmd, thanks for the info. Looks like it should be possible, but I like the way I've got it set up at the moment, and don't want to break anything right before my trip. (updates to chromeos can break crouton apparently, and running android apps requires changing chromeos to the dev branch)
I'll mess around with it when I get back, because once I'm back the chromebook won't be my only computer, and if it's out of commision for a bit that'll be fine.
If things work out well with this set up I'll do a Diary post on this chromebook. I should probably do a review either way... we'll see how much enthusiasm I have for that.