お知らせ：０７６はゲーム開発スタジオとなる為、４月２日をもって０７６萌ＳＮＳ及び０７６萌Mitraのサービスを終了致します。諏訪子様は、新しいスタッフ専用のMitraインスタンスで引き続きフォロー出来ます。

これまで０７６萌ＳＮＳ又は０７６萌Mitraをご利用頂き、誠に有難う御座いました。

Conversation - ０７６萌ＳＮＳ

お知らせ：０７６はゲーム開発スタジオとなる為、５月２日をもって０７６萌ＳＮＳ及び０７６萌Mitraのサービスを終了致します。諏訪子様は、新しいスタッフ専用ののMitraインスタンスで引き続きフォロー出来ます。これまで０７６萌ＳＮＳ又は０７６萌Mitraをご利用頂き、誠に有難う御座いました。

Public
- Public
- Network
- Groups
- Popular
- People

Conversation

Notices

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Thursday, 09-Feb-2023 02:16:13 JST shitpisscum
@graf @miklol2 Ok just noticed something, since migrating to the new db there are barely any new activities added to the db. Look at the times, on the old "broken" db there used to be a few new activities every minute (which makes sense) and now there are gaps of 10+ minutes without any new activities, meaning the db definitely wasn't restored properly. My question is, is it worth even attempting to fix it or should I just drop and restore from the backup again?

cc @p @sjw
In conversation Thursday, 09-Feb-2023 02:16:13 JST from social.mrhands.horse permalink
Attachments
1. Untitled attachment
  https://social.mrhands.horse/media/3346b12f-a84a-4fd1-9ff1-515e159d0c48/activitiesTime.png
- :btrfly: anime graf mays 🛰️🪐 (graf@poa.st)'s status on Friday, 10-Feb-2023 06:50:59 JST :btrfly: anime graf mays 🛰️🪐
  in reply to
  @shitpisscum @sjw @1ns0mniak @p @miklol2 wait you didn't restore it to a different version of postgresql did you? theoretically it shouldn't work but I'm just making sure
  
  In conversation Friday, 10-Feb-2023 06:50:59 JST permalink
- 1ns0mniak (1ns0mniak@cyberstorm.one)'s status on Friday, 10-Feb-2023 06:51:01 JST 1ns0mniak
  in reply to
  @p @sjw @miklol2 @graf @shitpisscum Pelroma? Yo that happened to me as well. I updated everything, both postgres and pleroma and now it's running nice and cool.
  
  Assuming thats what you're talking about, I'm drinking and watching Dr. Phil atm.
  
  In conversation Friday, 10-Feb-2023 06:51:01 JST permalink
- shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:51:01 JST shitpisscum
  in reply to
  @1ns0mniak @sjw @p @miklol2 @graf Ok but here's the weird part: I migrated the db to a more powerful dedicated server and now it's running much WORSE than it was
  
  In conversation Friday, 10-Feb-2023 06:51:01 JST permalink
- pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Friday, 10-Feb-2023 06:51:02 JST pistolero :thispersondoesnotexist:
  in reply to
  @shitpisscum @sjw @graf @miklol2 DB server should be I/O-bound. What is it grinding that hard?
  
  In conversation Friday, 10-Feb-2023 06:51:02 JST permalink
- shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:51:03 JST shitpisscum
  in reply to
  @sjw @p @miklol2 @graf
  > just let it run for a little bit
  It's been running like this for 3 days already, CPU on the db server constantly at 100% so I don't really think it's going to fix itself any time soon lol
  
  In conversation Friday, 10-Feb-2023 06:51:03 JST permalink
- Your New Kemono Waifu :verified: :cornbread_the_cat: (sjw@bae.st)'s status on Friday, 10-Feb-2023 06:51:04 JST Your New Kemono Waifu :verified: :cornbread_the_cat:
  in reply to
  @shitpisscum @p @miklol2 @graf huh. Maybe just let it run for a little bit and see if it fixes itself.
  
  Check your db tuning as well
  
  In conversation Friday, 10-Feb-2023 06:51:04 JST permalink

Public

Conversation

Notices

Feeds