JATth

I wish lemmy communties existed for:

• 1. How are you doing today?
• 2. Did you discover anything new to your consciousnesses today?
• 3. I fucke’ed today. Here is how.

Edit: yeah, I think I miss a few of the old subreddit’s. Even if there is an equivalent in lemmy, such communities are quite silent.

You want benzodiazepines? They are basically erase memory from [0.00 to 24.0] so I definitely wouldn’t recommend.

I try to filter out most of this negative stuff, but it has a downside. You become disconnected from the raw information feed if you don’t occasionally just look at it. For short periods, it’s tolerable, but then I just re-enable all filtering to reduce my cognitive load.

If I need to be cheered up, I prefer to look for science articles or news since these are generally about unbiased progress.

I put too way too much effort in this reply… Yes… it’s nerve racking, especially if you are resorting to BIOS flashback to boot the CPU on an older (new) board.

Can’t get visuals (except maybe leds/indicators on the motherboard itself) when your CPU is incapable of accessing the ram or the devices yet. All external devices normally communicate through the RAM. (And by external, I mean not on the CPU package) Yet, the CPU has to solve out this chicken-and-egg problem of how to progress from the cold-boot without knowing what external RAM is installed. There are plethora of timing/clock-cycle/voltage settings for one stick of ram, which are tested on POST. Establishing sane DDR5/4 parameters is non-trivial. (I think it is order of +20!, twenty factorial: 2432902008176640000, if there were no starting point of XMP, JEDEC etc.)

I use hand tuned settings for DDR4, and on cold boot, the BIOS adjust the settings which I didn’t forbid it to do. Unless I unplug the PSU from the wall, the BIOS won’t retrain the memory again. I suspect my settings still aren’t 100% stable. (over period of years) Non-cold-boot assumes the ram works 100% same on each power up. If some OC setting drifts past a threshold once the system is heat soaked or receives more EMI interference, this could provoke a crash/BSOD etc. in absurd theory having a busy wifi router next the ram could cause the bios to select more robust/conservative settings to counter the EMI interference. Would be fun to know, if this would be true.

NO.

I watched YT channel that had rescue toucans and they belong to the wild. Every 5mins the owner reminds (and I believed he was/is a good owner) of this fact.

Funniest thing was the velociraptor mode and pure chaos. Saddest thing was seeing them die to health complications, despite the good care.

Welp, my only calculation was “64 cpu threads * 30% load -> ~19 cores busy”, I may be guilty of rounding up too much… The RAM usage is intresting however, since the kernel seems to be caching all it can, to point ejecting uneeded data into swap in order to retain the disk cache. If more ram is reserved by running processes, the (likely pict-rs, database services) disk access times will begin to degrade.

Thats ~19 cores pegged at 100%, eating 128GiB of ram (OS disk cache included) and bleeding onto swap. 🤯