DigitalDilemma

  • 3 Posts
  • 585 Comments
Joined 2 years ago
cake
Cake day: July 22nd, 2023

help-circle
  • DigitalDilemma@lemmy.mltoMicroblog Memes@lemmy.worldCritical thinking
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    5
    ·
    4 hours ago

    I went to school in the 1980s. That was the time that calculators were first used in class and there was a similar outcry about how children shouldn’t be allowed to use them, that they should use mental arithmetic or even abacuses.

    Sounds pretty ridiculous now, and I think this current problem will sound just as silly in 10 or 20 years.













  • Dynamic memory handling.

    On a machine where MariaDb is the primary service, I’d like to be able to set a variable in the config to tell it to use all the available memory apart from a sensible buffer.

    Something like: dynamic_memory_resizing_margin = 512M (Default would be 0, which would disable this behaviour)

    On startup, Maria would log in it’s primary log something like: “Dynamic Memory resizing in effect.” as a reminder to admins that it’s behaving in a non-standard way. It would also log if it was unable to resize down to its minimum footprint because, for example, something else was using more memory.

    Maria would then periodically (1 min?) check free OS memory and increases innodb_buffer_pool_size (and possibly other buffers) to make best use of the VM’s memory.

    Reasoning: I manage quite a few MariaDb instances on some 90 vms. These vary hugely between tiny databases, and huge, extremely busy databases. VM resources vary between 1Gb of ram up to 64gb. Currently I need to periodically review every server and adjust IBPS manually based on previous history. (We’ve had a lot of problem with malloc libraries allowing mariadb’s memory use to grow beyond what it should, so have very conservative margins to avoid ooms)

    (I understand Mysql 8 has something that promised similar to this but I’m not sure of the details as we don’t use it)






  • Every morning we wake up with the ability to change who we are and how we act and react.

    If you’re sincere, you’ll use that to improve who you are tomorrow.

    If you’re truly sorry, you’ll do something extra to help others in some way and address the karma imbalance you’ve caused. Apologise to those people you hurt. (Trust me, it will mean something to them) Find ways to help others survive bullying. Make anonymous donations to the places you stole goods from.



  • DigitalDilemma@lemmy.mltoLinux@lemmy.mlJackett memory leak
    link
    fedilink
    English
    arrow-up
    3
    ·
    28 days ago

    Others have answered why this isn’t a memory leak as such and is not as big a deal as you may think.

    But if you are still concerned, you can reduce it, even if doing so is a bad idea.

    1. You’re running it natively which means you’re probably using a systemd .service file to manage jackett. Research the .system setting “RuntimeMaxSec” - that will force a restart of the service every N seconds and prevent it growing. (This is a bad idea, but if you want to boss it around, you can)

    2. Run it in docker and force a max memory setting. Docker will prevent it using more than you set. You can also restrict cpu usage this way too. docker-compose example goes something like:

    deploy: resources: limits: cpus: 0.5 memory: 100m