Conversation

Notices

1. Embed this notice
   Ryle (ryle@awoo.fyi)'s status on Thursday, 24-Nov-2022 06:01:00 JST Ryle

   in reply to

   • pawlicker
   In a good setup, the compute VPSes getting trashed should not matter, because you should be able to deploy a new VPS and all your data is stored else where. Like database server and S3 storage. Of course, it then becomes a matter of ???
   • Embed this notice
     arcanicanis (arcanicanis@were.social)'s status on Thursday, 24-Nov-2022 06:01:00 JST arcanicanis

     in reply to

     • pawlicker
     Just a swap to a VPS with 'dedicated' cores versus 'shared' (at least per Linode's offerings; $30/mo v. $20/mo) was all that's needed to make a substantial difference. I'm sure if BEAM VM looks like it's eating spare processor cycles for busy-waiting, that the whole VPS itself starts to lose priority.
     https://stressgrid.com/blog/beam_cpu_usage/
     
     I guess I should have tried disabling the busy-waiting function, to see if that would have made just as much of a difference, before scaling up:
     https://docs-develop.pleroma.social/backend/configuration/optimizing_beam/#bad
     
     But either way, at least I have more predictable guaranteed performance now.
   • Embed this notice
     pawlicker (pawlicker@outpoa.st)'s status on Thursday, 24-Nov-2022 06:01:01 JST pawlicker
     protip don't use shit tier vpses without backups lmao