More > JRiver Media Center 26 for Linux

Is there any way to speed up views on a Pi?

<< < (4/5) > >>

JimH:

--- Quote from: Mastiff on October 05, 2020, 03:28:55 am ---Thanks, Jim! And that's actually not bad for this time of year here. Today I had around 2 meter waves... ;)

--- End quote ---
I've done about 1500 miles of open ocean sailing over the years, mostly on the North Sea.  Farsund ring a bell?

I fully appreciate how different it can be.

Thanks again for the pictures!

Mastiff:
Farsund is about 45 minutes drive west of Mandal, where I live. :) If I had known you were there (and if it was in a time when I knew who you are...) I'd taken the trip to buy you a beer! ;D

Mastiff:
Btw if that matters, I have tried running some intense stuff now (like library updates, clear library, mass tagging and so on), and the max CPU usage I see in the graph is just under 40 %. Shouldn't MC use more then that when it's available?

Awesome Donkey:
They might be single threaded tasks.

mwillems:

--- Quote from: Mastiff on October 06, 2020, 04:14:43 am ---Btw if that matters, I have tried running some intense stuff now (like library updates, clear library, mass tagging and so on), and the max CPU usage I see in the graph is just under 40 %. Shouldn't MC use more then that when it's available?

--- End quote ---

It's possible the tasks aren't multithreaded, but it's hard to tell what's going on without doing profiling (with tools like top or iotop).  A simple cpu graph won't tell you very much.

For example, a good way to get a sense of the "threadedness" of the work load is the "load" count (get by running "uptime" or looking at the top right of the display in the "top" command).  It tells you how many jobs are running or waiting for a processor at any given moment.  If the load count is higher than the number of processors you have, but you still have low CPU utilization, that tells you that the bottleneck is somewhere else.

Normally the bottleneck on a Pi is I/O not CPU.  If you're not seeing max CPU even on intense tasks its most likely that the CPU simply can't get data as fast as it can process it.  IF you run top and look at the third row, you can see the percentage of CPU usage in various activities.  "wa" is waiting for I/O.  If you see a high percentage there while running an intense task that will answer your question.  Another useful tool is "iotop", which can give you a sense of how much throughput is going on.  You'll probably need to install iotop though as its not there by default on debian like top and uptime.

Navigation

[0] Message Index

[#] Next page

[*] Previous page