@cassidyclown >non-fraudulently >not putting tyrone mcniggerman as legal name >not providing them with a fake ID scan in some latam/easteuro shithole in case they have concerns >not asking some kid on fiverr to shake his head on camera if even that fails
@cassidyclown@pwm Also if anything breaks on the VPS side, it's probably BuyVM's fault. One time they had two instances of the same VM running. Other time they literally force powered it off and never started it back up.
@0@cassidyclown@pwm I hosted all the instance media on it, and it was fine. Guess it is suitable as a data warehouse where things are mostly read, not written.
@pwm@0@cassidyclown Wrote a gigabyte file with dd both on the root filesystem and on a storage slab. 800 MB/s on root, ~500-600 MB/s on slab. Too lazy to do proper benchmarks, so I don't know what to gather from those results.
@mint@cassidyclown@pwm@0 I use it as a 3TB cache for all cached files and doing direct reads and writes to it was downright awful.
I decided to make it into a LVM PV, wrote a thin allocated file on the local SSD storage, turned that into a loopback device, and enabled LVM cache using that file. It's okayish now with the cache in front.
@7666@cassidyclown@pwm@0@mint discord does the same thing on GCP to get latency down, but it would probably still work well enough if postgres was told it had limited parallel io and random pages cost 4x the usual amount
still a shame pleroma fails so badly on a slow disk, crashing on a loop