Andres

@Fmstrat @veeesix The second, could you do raid across specific platters - yes and no. The drive firmware specifically hides the details of the underlying platter layout. But if you targeted a specific model, you could probably hack something together that would do raid across the platters. But given the answer to the first question, why would you?

@Fmstrat @veeesix Since there’s two very diffrent questions there… The first, “where do the failures happen?”: anywhere. It could be the controller dying (in which case the platters themselves are fine if you replace the board, but otherwise the whole thing is toast). It could be the head breaking. It could be issues with a specific platter. It could be something that affects _all_ the platters (like dust getting inside the sealed area). So basically, it very much depends.

@Zorque I’m saying that 14TB will only fit 280 (or more likely, less) of those ultra-hq movies, so 140TB (or, in the lead up to that, 100TB, since they’re talking about 5+ years or more before they even get close to 140TB) is reasonable for a 1,000-2,000 movie collection. Obviously I’m being loose with numbers, but the fact that one single movie can consume almost 80GB… well, you can start to understand consumer demand for 100+TB drives.

@Korkki @just_another_person I see 4k HDR blue ray movie rips these days on the order of 50GB (edit: eg, Eddington.2025.MULTi.VFF.2160p.DV.HDR.BluRay.REMUX.HEVC-[BATGirl]: 77.73G).

Which is too rich for my blood (I’m still watching on 1080p screens over here), but for someone with the right kind of home theater… that’s only ~280 movies on a 14TB drive. Lots of movie collections, even in the olden days of physical VHS and DVDs, span 1,000+ movies.

@SmoothLiquidation @Telorand They also claim up to 8x speed improvements with HAMR. Obviously that remains to be seen, but if they could roughly match capacity improvements, that would keep restriping in the same ballpark.

@dan @rimu Yep. For us, it was cheaper to use the VPS storage than S3 (at the time I took it over, in 2018). Amusingly, it was set up to use S3 for images but then mounted locally and served through the VPS’s web server, making it all painfully slow (the proper way would be to have the site provide links directly to the S3). By switching it to local storage, I cut hosting costs in half and also sped up the site by orders of magnitude.

@dan @goldensw The vast majority of traffic is going to be the first day or week that a new article is published, social media or whatever driving lots of traffic to that same article over and over. Loading the php interpreter each time, even if it’s reading cached data, *will* make the site fall over. Static files will not.

Though nowdays there’s stupid AI bots doing pathological stuff, so that may become an issue as well that requires some further adjustments.

@dan @goldensw Yes, this. I did almost exactly what you did (taking over maintenance of an older wordpress site used by a local news org), and it was in rough shape. The config is a bit crotchety (like most things wordpress these days), but we’re using WP Fastest Cache to create static html pages and a custom nginx configuration to read directly off those static pages (without hitting the php interpreter) for non-logged-in users. Basically try_files /…/cache/$uri, which falls back to php.

@illusionist At least with the demo that I’m looking at with the script to download, it gives both flatpak AND apt install commands, giving the user a choice. Maybe I’m looking at the wrong thing though?

@illusionist @henkster Firefox from apt and firefox from flatpak are not equivalent. The former goes through an extra process to remove non-free components.