[email protected] wrote: 
> Does Main-Stream Debian even use Pipewire and Wireplumber?

If one of the desktop environments is installed - KDE, GNOME,
XFCE4 - then pipewire generaly is. Wireplumber is an optional package.


> I observed what IS a problem on various Raspberry Pi 5, 8GB (default memory / 
> swap configuration) Running the newest Raspberry Pi OS (Debian GNU/Linux 12 
> -- Bookworm) at basically Standard temperatures and Pressures in clean, a low 
> to no RF environment.

Are you sure you're using actual Debian? The default for RPIs is
a Debian derivative - Raspberry Pi OS, which is apparently
modified in several ways.

> I don't know is these add-on programs are germane to Raspberry Pi OS or if 
> they might affect main-stream Debian distro users as well.

So.

> If you feel I should just take this up with the folks at Raspberry Pi, 
> they've advised me previously that the Raspberry Pi is marketed for children 
> to teach them programming skills.

The original was; I'm not sure how they can claim that with a
straight face at the current prices.

> I did walk away from that message feeling rather stupid that I had even been 
> using a child's computer as a workstation. I won't bother them again... or 
> buy any more of their product.

Reasonable. x86 miniPCs are not much larger and about the same
prices for less hassle.

> The problem I observed was running a lone simple BASH shell script using 
> IPSet, i.e.:
> 
> sudo ipset add MySet aaa.bbb.ccc.ddd/xx -exist
> 
> That works fine for about the first 200 or so IPv4. Then it starts losing 
> data.
> 
> Wireplumber (according to Gnome System Monitor and HTOP) ends up taking more 
> CPU time than the BASH script, where the BASH script is the only 
> user-initiated "program" in a desktop environment.
> 
> I think the problem there will be immediately obvious to you.

Not really, no. The "losing data" part is.


> To test my theory about Wireplumber and Pipewire, I inserted "sleep 5" 
> statements for every 10 lines of code, which code added IPv4's to MyList.
> 
> That extended how many sucessive (sorted) IPv4's I could add to the MyList, 
> without problems, to about 197 IPv4's.

This sounds like two problems:

1. ipset failing without giving an error. (Does it give an
error?)

2. Some kind of hardware problem, quite likely lack of I/O
bandwidth for storage.

> I recomnend using thousands of valid IPv4, in valid CIDR notation, to ensure 
> a clear and extended view of the problem. It's pretty simple to reproduce. (I 
> have checked the validity of the IPv4's CIDR many times.)
> 
> While the script only used about 20% of the 4 CPU's, when Wireplumber kicked 
> in, the CPU's started running at 80% to 100%, until (presumably) the BASH 
> script hit "sleep 5 statements. Then the load might subside briefly.

Note that I/O is easily confused with CPU utilization -- the
iotop package might help.



-- 
https://randomstring.org/~dsr/eula.html is binding upon you.
[Set the new password to "swordfish". Please repeat everything three times.]

Reply via email to