I always marvel at how long `tootctl self-destruct` takes to run.
-
I always marvel at how long `tootctl self-destruct` takes to run. And how sad it is killing an instance.
RIP historians.social.
(Don't worry, Union Place isn't going anywhere.)
-
I always marvel at how long `tootctl self-destruct` takes to run. And how sad it is killing an instance.
RIP historians.social.
(Don't worry, Union Place isn't going anywhere.)
And I thought the Sidekiq queue was just about empty... and it refilled. Doh!
The accounts pending deletion went down ... by 50 ... since nearly 2 hours ago. That's gonna take days at that rate.
-
And I thought the Sidekiq queue was just about empty... and it refilled. Doh!
The accounts pending deletion went down ... by 50 ... since nearly 2 hours ago. That's gonna take days at that rate.
And now we're about 5 hours in and still 2000 accounts to delete. Maybe about 200 completed. Zoinkies.
They sure don't incentivize being nice to other instances by self-dstructing properly...
-
And now we're about 5 hours in and still 2000 accounts to delete. Maybe about 200 completed. Zoinkies.
They sure don't incentivize being nice to other instances by self-dstructing properly...
Aha, so it's doing batches of 50 accounts at a time, and then waiting for the entire sidekiq queue to empty before doing another batch of 50.
Making the instance bigger so I can run more sidekiq workers, I guess...
-
Aha, so it's doing batches of 50 accounts at a time, and then waiting for the entire sidekiq queue to empty before doing another batch of 50.
Making the instance bigger so I can run more sidekiq workers, I guess...
Dramatically upsizing the instance and number of sidekiq workers is in fact clearing the queue much more quickly. Still like 1300 to go though...
-
undefined Luca Sironi shared this topic
undefined Oblomov shared this topic
-
Dramatically upsizing the instance and number of sidekiq workers is in fact clearing the queue much more quickly. Still like 1300 to go though...