Has javascript gotten slow?

Feb 27, 2025 Last reply: 1 year ago 6 Replies

Some months ago I purchased an Owon vds1022i usb oscilloscope. It uses a Java application for control and display.



Testing it with an old Pi2 running Bookworm and the default GUI showed very nice performance, with the screen updating the Owon control application fast enough that no delay was noticeable.



Now, several months and Bookworm updates later, I tried it again and the oscilloscope application updates the screen roughly once every five seconds.



Top reports about 0.6% user with the Java application not running, but close to 30% with the java application running but just sitting in the foreground with no inputs.



Are there any known problems with Java on Bookworm? I've tried disconecting other usb devices and swapping keyboards, that didn't help.



Is it possible to "roll back" the system by date? The initial tests that worked well were done in early August, 2024.



Thanks for reading,



bob prohaska


Java or Javascript? Javascript you'd run in a browser, Java you might download a .jar file and run it.

Theo

Not sure. The top window reports running java, but as I look at

formatting link
is a reference to python but no mention of java. Yet, java is what uses most of the cpu when I start the vds1022i control program. Is there some connection between the two?

Thanks for writing,

bob prohaska

It does mention Java.

formatting link
be the place to look for bug reports. I don’t see anything reflecting performance issues.

At any rate, a single application performing poorly is just not enough to conclude there’s a problem with the JRE. You’re more likely to be seeing poor behavior by the one application.

Contacting the maintainer of the oscilloscope application would be a reasonable approach (using whatever their preferred support or bug reporting channel is).

If you can find a copy of the JRE package from that time period then potentially yes. I’m not sure if the package binaries are kept anywhere (in principle they can probably be rebuilt from source, if not, but this is starting to turn into a lot of work for something speculative).

It appears the problem was Wayland. I was quite firmly convinced that the initial experiment was done with Wayland active, but evidence suggests otherwise.

Switching from Wayland to X11 seems to have restored the former level of performance. No other changes, I just set X11 active and rebooted.

I suppose it's possible there was a change to Wayland, quite a few updates were applied between August and now. Alas, it's far more likely I was simply mistaken about the initial test.

Thanks for everyone's attention, and apologies for the noise!

bob prohaska

Now that IS interesting. I would have expected that Wayland would be faster...

X is such and enormous pile of bloated excrement that Wayland must be very early stage design.

Nope. Its a really good nugget of info to tuck away.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required