OpenCPN (via openplotter) slow on RaspPi3

[Foeboat]

Hi,

First, I love low cost and functionality of OpenCPN on a Raspberry Pi. Maybe I am expecting too much speed-wise from OpenCPN on my RaspPi3 but I am looking for suggestions on how to speed it up. I have the version that is downloaded as part of the OpenPlotter package (reloaded a few days ago). I have AIS and GPS connected. I have NOAA RNC raster charts loaded. I have a largish (22 inch) HDMI monitor. My problem is the response time is slow (things like click and wait, charts don't appear quickly). Also, the AIS targets don't update very fast (more than a minute in some cases between updates). Is there anything I can do to speed things up? I would be greatfull for any suggestions (or pointers on where to look).

Thanks!

David

[waterman480]

While the Rpi3 has never been "snappy", it did have acceptable performance. Somehow, it has slowed down. I have seen memory usage gone through the roof for no discernible reason. Zooming works when it feels like it. For example if you use the onscreen + / - icons, it works normally for a few moments, then the increment becomes very small and erratic, for example scale 7400 (1.4x), 7450 (1.3x), 7450 (5.4x) 7500 (5.3x) Kernel version does not seem to matter - 4.9.41 or 4.9.35. On the Pi box, it does help with the initial scale values if you do a manual entry. ( I use 518 for a 24" screen) Otherwise I have to make adjustments. These issues do not show in Windows. I may do a build on my system to see if there was a problem with the libraries/compile. I have also had problems with O crashing, These systems were resuscitated by deleting all the entries for the dashboard except the position and setting the counter to 1 - so I don't know what item was causing the issue.

[waterman480]

Note that this may be a Pi issue, or a combination of the both Pi and O. I would not make it worse by trying GL drivers - both vc4-fkms-v3d and vc4-kms-v3d have issues that make it not worth the effort when you are trying to fix other problems.

[NahanniV]

Are you using Hardware accelerated graphics ?
OpenCPN->Options->Display->Advanced->UseAcceleratedGraphics

If you are using raster charts you might get better performance by enabling texture compression caching.
Options->Display->Advanced->UseAcceleratedGraphics->Options->TextureCompressionWithCaching
This will convert your raster charts into a format that is easier to feed to OpenGL. It will take more disk space. Also unless you run the RebuildTextureCache, the first time you access each chart it will need to be converted making it initially slower, building the cache can take a long time if you have a lot of charts.

[waterman480]

If you install Htop and GKwellm you can get a visual of what is slowing down your system. If it is read_sensors_d.py - checkout the pyplilot subject (pg3) on openplotter.

Cheers,

Dave

[verkerkbr]

Originally Posted by waterman480

If you install Htop and GKwellm you can get a visual of what is slowing down your system. If it is read_sensors_d.py - checkout the pyplilot subject (pg3) on openplotter.

Cheers,

Dave

You can see how fast the screen works with glxgears. You can get glxgears by installing mesa utils.

Here running at 145 FPS.

Latest kernel version and latest updates. OpenGL setting to on.

I'am using ENC charts.

Update the chart database.

Bram

[baltika_no_9]

Originally Posted by verkerkbr

You can see how fast the screen works with glxgears. You can get glxgears by installing mesa utils.

Here running at 145 FPS.

Latest kernel version and latest updates. OpenGL setting to on.

I'am using ENC charts.

Update the chart database.

Bram

Bram

I am getting about 60 fps with my RPi3, latest kernel and updates. I have OpenGL selected in OpenCPN. Are there any other settings you've changed?

Thanks

[baltika_no_9]

Originally Posted by waterman480

....... it does help with the initial scale values if you do a manual entry....... .

Dave would you mind elaborating on this comment please? forgive me as I am not sure what setting you're referring to.

Many thanks

[Foeboat]

Sorry, I'm a bit new at this. To install mesa utilities, I think I do this:

sudo apt-get install mesa-utils

then what?

[conachair]

Originally Posted by baltika_no_9

Bram

I am getting about 60 fps with my RPi3, latest kernel and updates. I have OpenGL selected in OpenCPN. Are there any other settings you've changed?

Thanks

Try
vblank_mode=0 glxgears

Though the hardware acceleration crashes Opencpn if I run raster kap google earth chart files on on the Pi. Quick with vector though.

[verkerkbr]

Originally Posted by baltika_no_9

Bram

I am getting about 60 fps with my RPi3, latest kernel and updates. I have OpenGL selected in OpenCPN. Are there any other settings you've changed?

Thanks

Hello Baltika,

I'am not doing anything special:

OpenPlotter latest update to Alpha 0.14.4
Latest Raspian kernel version 4.9.41 (sudo rpi-update)
latest Raspian updates: (sudo apt update and then sudo apt upgrade)
using the HDMI port for the screen
In OpenPlotter VNC, Wifi, SignalK and AIS SDR dongle are on. (Here at my home)

Using Glxgears without parameters.

And of course a fast SD card 32 Gb HC 1 (10) read 80

OpenCPN 4.8.0 with OpenGL on.

With the VC4 driver things are going much faster. But the VC4 driver is still not useable. Locks-up under certain movements.

Can be switched on or off in: sudo rpi-config > advanced > Experimental driver

But it works for my at a acceptable speed.

Bram

[baltika_no_9]

Originally Posted by verkerkbr

Hello Baltika,

I'am not doing anything special:

OpenPlotter latest update to Alpha 0.14.4
Latest Raspian kernel version 4.9.41 (sudo rpi-update)
latest Raspian updates: (sudo apt update and then sudo apt upgrade)
using the HDMI port for the screen
In OpenPlotter VNC, Wifi, SignalK and AIS SDR dongle are on. (Here at my home)

Using Glxgears without parameters.

And of course a fast SD card 32 Gb HC 1 (10) read 80

OpenCPN 4.8.0 with OpenGL on.

With the VC4 driver things are going much faster. But the VC4 driver is still not useable. Locks-up under certain movements.

Can be switched on or off in: sudo rpi-config > advanced > Experimental driver

But it works for my at a acceptable speed.

Bram

Thanks for this Bram

My set up is almost identical but I don't have an AIS SDR dongle and I was at v 4.9.35 of the kernel. I've updated that to .41 but that has made no change, glxgears is still around 60fps.

I am driving my monitor from the HDMI port but via an HDMI to VGA adapter into the VGA port in the monitor. Maybe I should try driving it straight HDMI.

Edit
Nope, straight HDMI made no difference.

Thanks again, much appreciated

[duichan]

Originally Posted by baltika_no_9

glxgears is still around 60fps.

glxgears must be run with the vblank prefix - i.e. "vblank_mode=0 glxgears"
Without this the speed will be limited by display blanking and will indeed never exceed 60fps.

[seandepagnier]

What movements locks up the vc4 driver? Texture compression, I think it's broken on the vc4 driver. I tried to build and it's not working. So unfortunately the compressed texture cache is probably either not working or much slower.

Also, keep in mind, opencpn is still really slow. I know it could be faster in a lot of ways, and it's possible to make it completely seamless through time.

[NahanniV]

Originally Posted by boat_alexandra

.... Texture compression, I think it's broken on the vc4 driver. I tried to build and it's not working. So unfortunately the compressed texture cache is probably either not working or much slower.
...

You would be a good person to report that problem to the VC4 developer.
You can speak his language.