spacecowboy
Interests in ML and social aspects of tech.
Building For You feed: https://bsky.app/profile/spacecowboy17.bsky.social/feed/for-you
Hobby project: linklonk.com
- Yes, For You was down for 30 minutes - the computer hanged and I had to reboot it to bring it up again. Not clear what caused it. One option is that there is an issue with power management. My system drive already used to have random hangs for ~30-60 seconds due to power state transitions.
- @spacecowboy17.bsky.social The best BlueSky feed seems to be down 😭
- I think I fixed the initial issue by disabling NVME power state changes with nvme_core.default_ps_max_latency_us=0 in GRUB_CMDLINE_LINUX_DEFAULT Will try a few more options to disable power state management: "pcie_aspm=off pcie_port_pm=off" Open to any other suggestions on how to solve this.
- A small tweak to reduce "Show less like this" in For You by 36%
- Launched the change. Here are the latest results. Started another small experiment comparing 50K max curators (default) vs 60K (new experiment). My expectations: - it won't affect the number of likes or "show less" - the request latency will increase
- The For You feed will be down for a few minutes. I need to restart the computer to try resolve Steam segfaults (probably another nvidia driver update?) Will use this opportunity to enable RAM EXPO profile (4800 -> 6000) which got reset during the CPU upgrade.
- We are back! The part that took more time than expected was removing the above canned message and redirecting the traffic back to the feed generator. The reason - the VS Code hanged during loading and I've been using it to run docker compose commands. Probably one of the extensions was misbehaving
- Checked if the EXPO profile got enabled and it looks like it hasn't, it's still at 4800 instead of 6000: $ sudo dmidecode -t memory | grep "Speed" Speed: 4800 MT/s Configured Memory Speed: 4800 MT/s Will try again next time I need to reboot.
- At least the reboot helped resolve the game launch issues.
