It looks like network traffic and steam survey data are very noisy. So it's every other month we get articles like "Linux hit a new percentage record" "Linux just fell down 2 percentage points, will it ever recover" The multitude of articles trying to click bait as much as possible is getting annoying after a while.
You don't need a video. You need marketing & communication 101. During covid I am sure some professors uploaded lectures to youtube, or pick up the book if it's more your jam. Think about what you want to communicate to a person coming across your project for the first time. Make bullet points and rank them. Then begin writing including all the information in that order.
A good readme would be sufficient. Go to some popular project and copy their structure of its readme in your project.
You are mixing up the units here. Value is not a real money, and you can't pay salaries with value. You can pay salaries with cash.
To actually get how many LOC in a kernel per person per year they produce. You need to look at git history, and do data science on it. It's doable and easy but not really my area of expertise.
You need to account for that vast majority of contributors make just one patch and they are never heard from again. They don't work full time, or even part time on the kernel.
I didn't remember that I participated in 2025 canvas as I didn't make a design on it. Technically I participated in all of them then, but on different alts.
It makes sense in Terry A. Davis/Temple OS sense. Someone mentally ill needs everything to be symmetrical. They substitute o with Ⓞ in www.gⓄⓄgle.com I think they use fancy unicode to have a bearable symmetrical font; And someday they found that they can upload stuff to github and they upload what they made.
At first glance there is a lot of noise that look like an ARG but there is just too much random stuff. There are some binary blobs that are marked as executable. They might be malware.
Edit:
Found blender screenshots, firefox screenshots with some firefox extension config files, SVGs and PNGs, links to alternative 4chans, solidworks tutorials and blender VK groups
They are crazy for using VERY heavily riced windows that is ultra-minimalist white.
Russian hacker for sure. Might or might not have developed malware. I am more inclined for this to be a cloud backup hosted on github.
I have started to dig more into the perf, trace-cmd and cyclictest and finally managed to run all of the in the same time to capture the same high delay event. If the arch forum is correct then pipewire uses data-loop.0 process for realtime processing. It got SCHED_RR, so it seems correct as according to man pages it would preempt the SCHED_OTHER that stress-ng runs in.
Interesting thing I (and a council of clankers) noticed in trace_cpu_4.txt is that the interrupt didn't fire at specified time, and when it did, scheduler immediately preempted stress-ng to run the cyclictest as it's SHED_FIFO.
systemctl status rtkit-daemon
● rtkit-daemon.service - RealtimeKit Scheduling Policy Service
Loaded: loaded (/usr/lib/systemd/system/rtkit-daemon.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Thu 2026-07-16 08:42:27 CEST; 3h 3min ago
Invocation: 71422e850ec74c97b6edfa1666d3243a
Main PID: 1599 (rtkit-daemon)
Tasks: 3 (limit: 16290)
Memory: 580K (peak: 3.5M, swap: 12K, swap peak: 12K)
CPU: 92ms
CGroup: /system.slice/rtkit-daemon.service
└─1599 /usr/libexec/rtkit-daemon
lip 16 08:42:38 bazzite rtkit-daemon[1599]: Successfully made thread 3090 of process 3090 (/usr/bin/pipewire) owned by '1000' high priority at nice level -11.
lip 16 08:42:38 bazzite rtkit-daemon[1599]: Successfully made thread 3095 of process 3090 (/usr/bin/pipewire) owned by '1000' RT at priority 20.
lip 16 08:42:38 bazzite rtkit-daemon[1599]: Successfully made thread 3091 of process 3091 (/usr/bin/wireplumber) owned by '1000' high priority at nice level -11.
lip 16 08:42:38 bazzite rtkit-daemon[1599]: Successfully made thread 3103 of process 3091 (/usr/bin/wireplumber) owned by '1000' RT at priority 20.
lip 16 08:42:39 bazzite rtkit-daemon[1599]: Successfully made thread 3296 of process 3296 (/usr/bin/pipewire) owned by '1000' high priority at nice level -11.
lip 16 08:42:39 bazzite rtkit-daemon[1599]: Successfully made thread 3300 of process 3296 (/usr/bin/pipewire) owned by '1000' RT at priority 20.
lip 16 08:42:41 bazzite rtkit-daemon[1599]: Successfully made thread 3837 of process 3287 (/usr/bin/plasmashell) owned by '1000' RT at priority 20.
lip 16 08:42:42 bazzite rtkit-daemon[1599]: Successfully made thread 4081 of process 3287 (/usr/bin/plasmashell) owned by '1000' RT at priority 20.
lip 16 08:42:43 bazzite rtkit-daemon[1599]: Successfully made thread 4331 of process 4070 (/var/home/ludrol/.local/share/Steam/ubuntu12_32/steam) owned by '1000' high priority at nice level -10.
lip 16 08:42:44 bazzite rtkit-daemon[1599]: Successfully made thread 4332 of process 4070 (/var/home/ludrol/.local/share/Steam/ubuntu12_32/steam) owned by '1000' high priority at nice level -10.
I tried to force a clanker to help me, but it can only get me so far.
I have run sudo perf sched record -- sleep 5 with spotify and stress-ng and without easy effects but it didn't really tell about what was blocking the thread, or what could be the problem.
-------------------------------------------------------------------------------------------------------------------------------------------
Task | Runtime ms | Count | Avg delay ms | Max delay ms | Max delay start | Max delay end |
-------------------------------------------------------------------------------------------------------------------------------------------
TaskCon~ller #4:(2) | 0.083 ms | 3 | avg: 8.605 ms | max: 22.177 ms | max start: 2225.534477 s | max end: 2225.556654 s
dex-thread-pool:(3) | 6.973 ms | 7 | avg: 8.459 ms | max: 22.054 ms | max start: 2227.176387 s | max end: 2227.198441 s
spotify:(5) | 390.149 ms | 855 | avg: 8.354 ms | max: 198.827 ms | max start: 2227.285930 s | max end: 2227.484757 s
WRScene~derLP#1:5028 | 2.360 ms | 194 | avg: 7.097 ms | max: 76.383 ms | max start: 2226.890377 s | max end: 2226.966759 s
ThreadPoolServi:8864 | 0.101 ms | 3 | avg: 6.935 ms | max: 20.742 ms | max start: 2226.356434 s | max end: 2226.377175 s
Media:8854 | 53.526 ms | 394 | avg: 6.881 ms | max: 107.856 ms | max start: 2226.212405 s | max end: 2226.320261 s
VizCompositorTh:8780 | 77.461 ms | 562 | avg: 6.859 ms | max: 83.443 ms | max start: 2227.253999 s | max end: 2227.337441 s
Core Thread:8688 | 7.656 ms | 105 | avg: 6.800 ms | max: 77.954 ms | max start: 2229.299488 s | max end: 2229.377442 s
Connect Discove:8725 | 0.286 ms | 8 | avg: 6.768 ms | max: 16.469 ms | max start: 2227.202786 s | max end: 2227.219255 s
Network Thread:8708 | 6.427 ms | 76 | avg: 6.677 ms | max: 40.636 ms | max start: 2229.901403 s | max end: 2229.942039 s
WRScene~ilder#1:5027 | 3.435 ms | 211 | avg: 6.582 ms | max: 79.265 ms | max start: 2226.887473 s | max end: 2226.966738 s
File Streamer I:8711 | 9.539 ms | 100 | avg: 5.854 ms | max: 44.024 ms | max start: 2227.061508 s | max end: 2227.105532 s
ThreadPoolForeg:(6) | 5.587 ms | 59 | avg: 5.745 ms | max: 32.582 ms | max start: 2225.737484 s | max end: 2225.770066 s
KIO::WorkerThre:(2) | 1.832 ms | 22 | avg: 5.452 ms | max: 20.065 ms | max start: 2229.568516 s | max end: 2229.588581 s
Desktop EventSe:8689 | 0.595 ms | 1 | avg: 5.057 ms | max: 5.057 ms | max start: 2225.703380 s | max end: 2225.708437 s
spotify:cs0:8750 | 15.509 ms | 245 | avg: 5.056 ms | max: 51.215 ms | max start: 2227.051346 s | max end: 2227.102561 s
VideoFrameCompo:8855 | 29.563 ms | 337 | avg: 4.979 ms | max: 47.150 ms | max start: 2227.483466 s | max end: 2227.530616 s
WRRende~ckend#1:5029 | 18.610 ms | 336 | avg: 4.894 ms | max: 69.204 ms | max start: 2227.019314 s | max end: 2227.088517 s
Chrome_IOThread:(2) | 9.801 ms | 132 | avg: 4.686 ms | max: 35.030 ms | max start: 2229.786608 s | max end: 2229.821638 s
glean.dispatche:4896 | 7.905 ms | 379 | avg: 4.599 ms | max: 71.021 ms | max start: 2226.969815 s | max end: 2227.040835 s
WebExtensions:5078 | 83.091 ms | 254 | avg: 3.902 ms | max: 43.411 ms | max start: 2227.657268 s | max end: 2227.700679 s
Chrome_ChildIOT:(5) | 38.349 ms | 940 | avg: 3.864 ms | max: 57.356 ms | max start: 2225.249786 s | max end: 2225.307142 s
ThreadPoolSingl:(2) | 37.049 ms | 570 | avg: 3.811 ms | max: 58.063 ms | max start: 2227.475541 s | max end: 2227.533604 s
TaskCon~ller #1:(2) | 5.080 ms | 83 | avg: 3.688 ms | max: 34.766 ms | max start: 2227.041677 s | max end: 2227.076443 s
TaskCon~ller #0:(4) | 17.486 ms | 162 | avg: 3.036 ms | max: 39.163 ms | max start: 2227.452333 s | max end: 2227.491496 s
Audio Driver Th:8718 | 15.663 ms | 513 | avg: 2.887 ms | max: 48.186 ms | max start: 2227.368253 s | max end: 2227.416439 s
firefox:cs0:4943 | 4.029 ms | 56 | avg: 2.884 ms | max: 9.819 ms | max start: 2228.624509 s | max end: 2228.634328 s
Renderer:4966 | 16.666 ms | 133 | avg: 2.751 ms | max: 36.844 ms | max start: 2227.794477 s | max end: 2227.831321 s
bazaar:8465 | 0.190 ms | 3 | avg: 2.720 ms | max: 8.111 ms | max start: 2227.223328 s | max end: 2227.231439 s
IPC I/O Parent:4898 | 5.250 ms | 206 | avg: 2.573 ms | max: 22.691 ms | max start: 2227.468762 s | max end: 2227.491453 s
Media Mixer Ren:8882 | 39.110 ms | 478 | avg: 2.484 ms | max: 39.760 ms | max start: 2229.637725 s | max end: 2229.677485 s
mpris-proxy:2576 | 0.648 ms | 5 | avg: 2.477 ms | max: 5.067 ms | max start: 2226.065870 s | max end: 2226.070938 s
JS Watchdog:(5) | 0.480 ms | 21 | avg: 2.434 ms | max: 23.796 ms | max start: 2226.863646 s | max end: 2226.887442 s
SteamUIWatchdog:4443 | 0.025 ms | 1 | avg: 2.391 ms | max: 2.391 ms | max start: 2229.533194 s | max end: 2229.535585 s
DOM Worker:15552 | 4.313 ms | 28 | avg: 2.111 ms | max: 8.721 ms | max start: 2225.547973 s | max end: 2225.556694 s
Compositor:(2) | 125.776 ms | 2106 | avg: 2.076 ms | max: 119.343 ms | max start: 2229.776914 s | max end: 2229.896257 s
Timer:(10) | 8.823 ms | 416 | avg: 2.054 ms | max: 42.432 ms | max start: 2226.970019 s | max end: 2227.012451 s
dolphin:9296 | 31.250 ms | 117 | avg: 1.963 ms | max: 21.491 ms | max start: 2228.605754 s | max end: 2228.627245 s
TaskCon~ller #3:(2) | 1.196 ms | 35 | avg: 1.848 ms | max: 22.169 ms | max start: 2225.534467 s | max end: 2225.556635 s
TaskCon~ller #2:(2) | 3.287 ms | 50 | avg: 1.644 ms | max: 22.594 ms | max start: 2225.534012 s | max end: 2225.556605 s
pipewire-loop:8884 | 20.933 ms | 511 | avg: 1.583 ms | max: 42.681 ms | max start: 2227.302468 s | max end: 2227.345149 s
[…]
pipewire-pulse:3296 | 19.050 ms | 727 | avg: 0.123 ms | max: 0.994 ms | max start: 2229.906447 s | max end: 2229.907441 s
Interesting that the claim couldn't be replicated. It could just be false positive.
Googled it and this came out: https://musescore.org/en/node/14318
It looks like network traffic and steam survey data are very noisy. So it's every other month we get articles like "Linux hit a new percentage record" "Linux just fell down 2 percentage points, will it ever recover" The multitude of articles trying to click bait as much as possible is getting annoying after a while.
You don't need a video. You need marketing & communication 101. During covid I am sure some professors uploaded lectures to youtube, or pick up the book if it's more your jam. Think about what you want to communicate to a person coming across your project for the first time. Make bullet points and rank them. Then begin writing including all the information in that order.
A good readme would be sufficient. Go to some popular project and copy their structure of its readme in your project.
You are mixing up the units here. Value is not a real money, and you can't pay salaries with value. You can pay salaries with cash.
To actually get how many LOC in a kernel per person per year they produce. You need to look at git history, and do data science on it. It's doable and easy but not really my area of expertise.
You need to account for that vast majority of contributors make just one patch and they are never heard from again. They don't work full time, or even part time on the kernel.
I didn't remember that I participated in 2025 canvas as I didn't make a design on it. Technically I participated in all of them then, but on different alts.
It makes sense in Terry A. Davis/Temple OS sense. Someone mentally ill needs everything to be symmetrical. They substitute o with Ⓞ in www.gⓄⓄgle.com I think they use fancy unicode to have a bearable symmetrical font; And someday they found that they can upload stuff to github and they upload what they made.
At first glance there is a lot of noise that look like an ARG but there is just too much random stuff. There are some binary blobs that are marked as executable. They might be malware.
Edit:
Found blender screenshots, firefox screenshots with some firefox extension config files, SVGs and PNGs, links to alternative 4chans, solidworks tutorials and blender VK groups
They are crazy for using VERY heavily riced windows that is ultra-minimalist white.
Russian hacker for sure. Might or might not have developed malware. I am more inclined for this to be a cloud backup hosted on github.
Edit2: The Filepath is crazy
If you have time you could implement an experiment in piefed or lemmy to test how it feels.
I guess there are sociology books written about it, but I don't know any.
I have ruled out the RAM issue by running as simplified test as possible: spotify + stress-ng and easy effects not running
I have started to dig more into the
perf,trace-cmdandcyclictestand finally managed to run all of the in the same time to capture the same high delay event. If the arch forum is correct then pipewire usesdata-loop.0process for realtime processing. It got SCHED_RR, so it seems correct as according to man pages it would preempt the SCHED_OTHER that stress-ng runs in.Interesting thing I (and a council of clankers) noticed in trace_cpu_4.txt is that the interrupt didn't fire at specified time, and when it did, scheduler immediately preempted stress-ng to run the cyclictest as it's SHED_FIFO.
My current theory is some sort interrupt problem
trace-cmd report > trace.txtsed -n '2682652,2684299p' trace.txt > trace_extract.txtcat trace_extract.txt | grep -i "\[004\]" > trace_cpu_4.txtlogs:
sudo perf sched timehist > perf_timehist.txtawk '$1 >= 9980.792239 && $1 <= 9980.797096' perf_timehist.txt > perf_extract.txthttps://pastebin.com/iuB98bXgsudo perf sched latency > perf_latency.txthttps://pastebin.com/JP0PfrSUAfter digging a bit it looks like pipewire and spotify don't get realtime shedules only SCHED_OTHER and SCHED_BATCHhttps://bbs.archlinux.org/viewtopic.php?pid=2279287#p2279287I tried to force a clanker to help me, but it can only get me so far.
I have run
sudo perf sched record -- sleep 5with spotify and stress-ng and without easy effects but it didn't really tell about what was blocking the thread, or what could be the problem.https://pastebin.com/nZnGf2fP
clanker has seen
cyclictestandsudo trace-cmd record -e sched -e irq -e timer -e workqueue -e power -e signalso I tried running thatI have extracted the scheduler events between ~8ms delay of 16705 thread, but I don't know how to tackle it.
https://pastebin.com/D4bbzqT7
Thanks. Looks like I am one of lucky 10000 to learn about real time schedulers.
I have read through the article and I am 99% sure it's schedule issue
after dozens of seconds without load I get this output:
tested
default.clock.ratewith 44100 and 48000 it still crackles,#default.clock.allowed-ratesis commented outclosing easyeffects helped with VLC, but it still crackles occasionally in MPV and frequently in spotify
journalctl has no messages generated when crackling.
edit: reading through the pw-top article and it might give me clue
when running
stress-ng --timeout 30s --cpu 12it still happens so it's not RAM issueClickbait title but cool data science
I have my (1) project as homepage, if it doesn't load on browser startup then I have ze problem. (I am a monster with disabled tab restoring.)
IDK what I will do if I will have more than one, but that's future me problem.
Cool. too early in development to use in my robot as I don't see any mention of ROS2 in the wiki.