@dcc@ins0mniak@NonPlayableClown@vic It literally doesn't. I've tried to fix it for months before just giving up. It's a broken mess and the "meta" part of didn't seem to work after I updated somewhere in September. It always just returned results from one engine even though it showed that other ones responded.
@7666 Yeah, I've been fighting performance issues since I moved the Pleroma DB to a slab and there's basically no way to solve it. It just chokes randomly for a few minutes multiple times a day and comes back. Even the OS SSD sometimes just gives up.
@7666 It's probably an IOPS quota over some time frame, many VPS providers do that. OVH being one of the worst offenders. After around 2GB, their additional disk throttle to 12,10,8,4 MB/s of sustained read or write. Slowly throttling down as you keep using the disk.
What I usually see is an almost increase in disk backlog to around 5-10 seconds for 15-20 minutes and then it goes back to normal. A reliable way to trigger it is to open a few tabs of random bigger threads, or make many search queries. It's not related to an increase in network traffic/requests, dmcache deciding to write the dirty pages to the primary disk or PostgreSQL deciding to do DB maintenance. It just happens out of nowhere unprovoked. number of IOPS by type and disk Backlog by disk
@7666 Also about the Miami storage slab being completely dead and corrupted. From what Fran said in Discord, they only have a single slab node there, so if the FS (probably ZFS) can't recover at least some of it, it's probably gone. The way he said it, implies to me that there's basically no backup other than the RAID 10 redundancy.
@7666 I'm not moving completely away yet. If the LUX nodes end up in NL, I'm moving those immediately, the rest will stay unless Hannan proves he's a nontransparent money seeking retard like I sort of expect.
If I end up migrating completely, it will be a massive pain in the ass and self-hosting at home isn't really a painless option either thanks to the EU being stupid like they've always been.
@7666 The owner of Cloudzy AI (and .com) and Fran know each other since before BuyVM existed and BuyVM is using some of their infra already, so it isn't a completely random company that bought the brand name. However since Cloudzy is operated from UAE a lot of question around UAE laws and US laws come into question. What about free speech, government involvement in infiltrating the infra and much more. And since neither Fran nor Hannah (the owner of Cloudzy) answered any question about that for more than a week, I'm kinda worried. UAE isn't really the perfect country where you want to have your hosting business registered.
@7666 I wouldn't worry about paying up for bandwidth _for your current services_. The contract they signed includes a clause where BuyVM has to have the same policies as they did before acquisition with the same pricing. However new services might be priced differently.
It might be that the same pricing and features must also apply to newly bought services, but I would have to read the hundreds of messages on Discord again for that. obrazek.png
@7666 I'm honestly having my doubts about BuyVMs future without him, because he said multiple times he isn't as interested in running a VPs provider as he used to. His main thing now is Namecrane (email and cpanel hosting)
@xianc78@rher You are barking at the wrong tree. These people will never change nor understand. That's why they are only worthy of getting laughed at. Especially Suiseiseki.
@p@Suiseiseki@xianc78 It does suck, but it's still better than being source-available. The worst part of is probably the requirement to publish your modified source even when used privately. It's not FSF approved, because they disagreed with that part of the license.
@Suiseiseki@p@xianc78 >>The main problem of "FreeDOS" is that you can't compile it without a proprietary compiler. >https://www.freedos.org/about/devel/ >https://github.com/FDOS/kernel/blob/master/build.bat#L10 >https://gitlab.com/FreeDOS/base/fdisk/-/blob/master/SOURCE/FDISK/Makefile (OpenWatcom) >https://gitlab.com/FreeDOS/base/fdisk/-/blob/master/SOURCE/FDISK/Makefile.gcc (I16 Gcc) >OpenWatcom (OSI approved, ie not proprietary) >NASM (BSD 2-clause, ie not proprietary) Again, you don't even know what you are talking about.