• 7 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: February 16th, 2024

help-circle

  • Counterpoint; it required gigabit internet and still had noticable delay to my eyes. It also had compression artifacts as well as low-medium graphics settings. It also hitched semi-regularly for no apparent reason.

    All the above meant that stadia was only good for people with the money to spend on it and located in an area with fast internet and didn’t play any FPSes. It was too many requirements to be a popular thing, kinda like VR is.

    It also suffered from the “games get removed straight from my library” problem. They also couldn’t support every game, or even the bare minimum if most popular right now, simply because they had to make sure it’s supported on their backend.

    It should have stuck around, but I don’t think it would be a big thing until much later when internet is actually decent in most places, instead of a very select few.






  • fstrim.service is disk tool (that’s supposed to only be run once a week, not every time you boot) that automatically cleans up old deleted SSD data. https://opensource.com/article/20/2/trim-solid-state-storage-linux

    It looks like it’s running too often, or on the wrong devices, every time you boot your computer. You can actually safely disable it; https://askubuntu.com/questions/1165128/fstrim-is-causing-high-boot-time but it’s worth looking into why it’s taking so long and being run so often.

    Running this should show you the log results of fstrim doing it’s thing without actually doing anything; sudo fstrim --fstab --verbose --dry-run

    These two will show the status of fstrim and it’s autorun service;

    systemctl status fstrim

    systemctl status fstrim.timer

    I got most of this from a quick google search; https://duckduckgo.com/?q=fstrim.service+systemd+slow You can do the same for the other major time-takers on your boot list. For comparison, here’s the top results of my semi-fresh install of linux mint;

    dageek247@mintPC:~$ systemd-analyze blame 2.237s NetworkManager-wait-online.service 2.077s systemd-binfmt.service 2.003s systemd-resolved.service 1.976s systemd-timesyncd.service 1.916s fwupd-refresh.service 1.365s logrotate.service 1.326s NetworkManager.service 933ms fwupd.service 401ms blueman-mechanism.service 334ms udisks2.service 263ms apt-daily-upgrade.service 254ms dpkg-db-backup.service 229ms dev-nvme0n1p3.device 215ms accounts-daemon.service 201ms power-profiles-daemon.service 199ms polkit.service 197ms smartmontools.service 183ms rsyslog.service 173ms ubuntu-system-adjustments.service 169ms systemd-udev-trigger.service 156ms user@1000.service 155ms proc-sys-fs-binfmt_misc.mount 146ms ModemManager.service 132ms apparmor.service 123ms avahi-daemon.service 121ms bluetooth.service 114ms grub-common.service 111ms lm-sensors.service 106ms switcheroo-control.service 105ms secureboot-db.service