Conversation

Notices

1. :archlinux: :nyarch: :verified: (lewdthewides@hidamari.apartments)'s status on Saturday, 02-Mar-2024 00:06:50 JST :archlinux: :nyarch: :verified:

   • スカイラー🎄🇷🇺 :z:
   • Tadano ❄️🎅
   • p
   @p @Tadano @skylar I've been pruning objects a couple times a year, and I haven't had any problems. The only problem so far that did manifest was we get 500 errors when opening some user profiles, but that could also be caused by the query trying to access data that's outside the LVM cache, and as others said, Frantech's block storage is horrible with random reads. I can see the query timing out after 15 seconds and constantly retrying as long as the profile is being viewed
   
   Maybe I started this instance after some major bug with object pruning was fixed, so that's why I never had problems
   •  (mint@ryona.agency)'s status on Saturday, 02-Mar-2024 00:06:49 JST 

     in reply to

     • スカイラー🎄🇷🇺 :z:
     • Tadano ❄️🎅
     • p
     @lewdthewides @Tadano @skylar @p I think p had a patch that noops some background activity pruning tasks, I applied it to my instance from day one.
   • :archlinux: :nyarch: :verified: (lewdthewides@hidamari.apartments)'s status on Saturday, 02-Mar-2024 00:20:10 JST :archlinux: :nyarch: :verified:

     in reply to

     • 
     • スカイラー🎄🇷🇺 :z:
     • Tadano ❄️🎅
     • p
     @mint @Tadano @skylar @p funny enough, it was your fba bot that I first noticed the 500 errors. The errors when away when I set up a test instance backed by a nvme drive using our database backup
      likes this.