• 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle

  • Really depends on many factors. If you have everything in RAM, almost nothing matters.

    If your dataset outgrows the capacity, various things start to matter, based on your workload. Random reads need to have good indices (also writes with unique columns), OLAPs benefit from work_mem, >100M rows will need good partitioning, OLTP may even need some custom solutions if you need to keep a long history, but not for every transaction.

    But even with >B of rows, Postgres can handle it with relative ease, if you know what you’re doing. Usually even on a hardware you would consider absolutely inadequate (last year I migrated our company DB from MySQL to Postgres, and with even more data and more complex workflows we downsized our RAM by more than half).





  • It’s voice and video calling with chat and screensharing. I intend to use it for a language school. It’s extendable, for instance you can also self-host a whiteboard, where everyone can draw. You can see the drawing in real time, which is good for asian languages, where direction of the stroke is important.

    Free, open-source, packaged in Debian, runs without issues, used it with friends for multi-hour voice chats during gaming nights.

    On the server you can configure things like FPS for screenshare. I have yet to adjust that and try streaming video/game through it.






  • Postgres is far superior in every way.

    We used MySQL (and Percona XtraDB) servers at work, and it is so bad. So I made several presentations showing generic and specific reasons why Postgres is better. I had to cut a lot of content because MySQL is just that bad.

    Some things may not seem relevant now, but as you keep the DB around long enough, you will appreciate the whole package of Postgres.

    Things that will help a lot, but are extensions:

    • pg_partman - for automatic partition management
    • patroni - management of replicas, automatic failover - it does everything for you with simple commands

    There is a DB comparison matrix, but hasn’t been updated in over a year, which is a shame, but still gives you the idea of how different databases support SQL features: link.

    Spoiler: postgres has the most support, with a huge lead

    Edit: MySQL is dead last, btw







  • msage@programming.devtoSelfhosted@lemmy.worldWhy docker
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    I have VMs on my metal, one specific for containers.

    Though I use LXC. Docker started with LXC, then grew bigger, and I don’t like how big it is.

    If I can set up one simple NAT and run everything inside a container, I don’t need Docker.

    Docker’s main advantage is the hub.