default-settings VS repo-release

I suffer from this issue across different linux distros and found that it is indeed a btrfs related issue. Have a read here and tinker around the suggested sysctl values https://github.com/pop-os/default-settings/issues/111

This has already been done https://github.com/pop-os/default-settings/pull/172

Pop uses zram by default now, so unless you're planning to set up hibernation you don't need a separate swap partition.

The default swappiness in Pop has been 10 since 2019

/u/jadero I've been experimenting with a zram optimization for Pop lately. I suspect that a great deal of remaining issues could be caused by memory pressure behaviors. https://github.com/pop-os/default-settings/pull/163 There's some tweaks in here that seem to be yielding great results from the few people that have tested it so far.

Personally, I follow the pop-os/repo-release repository so that I get notices of what is being updated and when and I can gauge what looks OK or not. I've caught a few things that looked wrong before and I have been able to provide feedback and sometimes fixes (eg. https://github.com/pop-os/default-settings/pull/145).

Watch for https://github.com/pop-os/repo-release/pull/242

The last release of cosmic packages to the release repository was yesterday.

Nope. Not a chance. See the updates

The pop-os/repo-release repository is the package release mechanism in Pop!_OS, and GitHub generates atom feeds for it. Each commit to this repository lists the packages that were released. Each package listed has a URL to a source code comparison between the previous released revision and the newly-released revision.

Or to specify what the last update was. One person's last update could have been someone else's update 3 months ago. The last update we released was 6 days ago.