Salamander

  • 1 Post
  • 15 Comments
Joined 3 years ago
cake
Cake day: December 19th, 2021

help-circle








  • I would kill. 2X growth rate is too fast, and it is easily better 100 random people now than 200 immediately after.

    What about these rules?

    • The group of people in the tracks is randomized every time.

    • The group always includes the person that the current decision maker loves the most.

    • The choice is to kill, or to increase the number of people in the kill group by one.

    • If the number of humans available reaches the population number, everyone dies.

    • The list of every decision made by every decision maker is public knowledge.

    • You are the first decision maker.


  • Sure! The comments that are posted from within your instance are labeled with “local = true”, even if they are posted to other instances. So the query below will dump all of the database entries for comments in your instance into a file. Assuming that you have a docker install.

    docker exec LEMMY_POSTGRES_CONTAINER_NAME psql -U POSTGRES_USER -c "select * from comment where local=true order by comment.published desc;" > all_comments.txt

    This will print to a file the comment table including all of the comments posted from within your instance, starting with the newest post. It is possible to combine other queries (such as associating the creator ID with the username), and then parse the output to produce a more informative and easy-to read output. But what I have shown might be enough for you. I may be able to help you if you need a more specific query.


    1. Not super easily. It can be done by querying the postgresql dabase, but there is no built-in method to do it using the browser interface at the moment. When anyone from any instance does report them, you will see the report.

    2. Someone please correct me if I am wrong. But, as far as I am aware, if you purge a user from your instance, that action is federated to every other instance - so if you respond quickly to these reports, other instance’s admins will not need to deal with them themselves. It is only when you perform an action on a user from a different instance that the action is only local.


  • Salamander@mander.xyzOPtoLemmy Support@lemmy.mlCPU load spikes
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    The spikes disappeared after I increased the RAM from 2 GB to 3 GB, and they have not re-appeared over the past few hours.

    It appears like some some process was hitting the 2GB RAM limit - even though under normal use only about 800GB of RAM are allocated. At first I thought that the high amount of read IOPS might be due to the swap memory kicking into action, but the server has no allocated swap.

    The postgresql container appears to fail when all of the RAM is used up, and it may be that the high CPU usage is somehow related to repopulating the dabase as it is restarted… But I would think that if this were the case I would see similar spikes whenever I reboot - and I don’t.

    Conclusion: I am not sure why this happens.

    But if anyone else notices these spikes it may be a RAM issue. Try increasing the RAM and see if they go away.