Syea
ELast I looked into it though (at least for sway) It has to be dependent on the window versus desktop because of something with wlroots. I'll have to read up on it again
Kit's still using CFQ
Kno kernel patches at all
KAll it does is disable bundling (so nice values can work)
Kand then use a rule system and DE plugin to set nice values on applications based on rules and which window is focused
Klastly, it tunes CFQ to the default settings on battery, and the Zen settings on power
Kthe builds in my copr tune it to use the Linux-TKG CFQ settings instead of Zen
SHey @KyleGospo How would I enable "system76-scheduler", do I just copy the files you mentioned to /usr/etc/... here on my repo?
Kwon't need any files at all, just install from copr and enable the service
Ksee bazzite's containerfile
Sah so they are not needed?
Sthe zram-generator etc.
Sfiles
Kspecifically for system76-scheduler
Kthe others each do their own little things
Sah so they dont "hurt"?
Swhat if i use the recipe.yml file?
Scan i just add them to the dockerfile?
Kyea
Sok good, does the line matter?
Sand exacly what do i add
WA lot of this low level stuff is really new to me.
Sis it just ?
S@KyleGospo
EThat'll do it
Sok good!
EIt's installed right?
Syea
EOkay
Salso
Scould you help with this? https://discord.com/channels/1072614816579063828/1084120222400774325/1134140475272605716
XI was thinking for the system76-scheduler service, does that need to be layered or can it instead run inside a container and by passing through the host dbus socket?
KI haven't tried, but applications like btop work great in a container
Kit's fairly likely it'd work fine
Xit seems to work if I pass
/run/dbus/system_bus_socket/etc/dbus-1/system.d/com.system76.Scheduler.confvery nice
Bthat's pretty cool
KGitHub
Reduce the amount of layers by keeping RUN and COPY to a minimum
Kwould love some extra eyes on this, big change from how we were doing things and I'm only going off what I've read so far regarding layer count & size
JI don't know enough to know other than I am very interested in the resulting difference
KBefore (Saving this for when I can get an after)
message.txt5.45KB
KLayers data for this
message.txt16.93KB
RWhen proper support for handling the OCI layers is implemented in whatever package, wouldn't you want to have multiple layers so you're only pulling the changed layers, rather than everything?
E.g. pulling the 20MB for that added package rather than all 3GB of the image each day
E.g. pulling the 20MB for that added package rather than all 3GB of the image each day
Kthere an issue for this?
Kmuch prefer that
GI'd check out bootc
GIdk if they will do it there but that's the future of ostree native containers
