• 9 Posts
  • 610 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle

  • Non-ECC memory controllers don’t really track the flow of information in and out, the same way your CPU can’t track that as well until it hits a register. CPU and Memory use clock speed regulated by voltage to pass data back and forth with no gates between, so there isn’t a way to directly monitor and get feedback about the flow of information until it hits a destination that does report back or gatekeep for whatever it is (performance registers for example).

    You can view the frequency of your running memory, which should give you an idea of the speed at which things will pass in/out, but that’s about all you’re going to get unless you find a utility that pulls a bunch of information from /proc and consolidates it all, but even then I believe you’d only be seeing an approximation and not live feedback about what’s passing through memory.











  • There is no way to do what teams does without significant infrastructure. Same with Slack and others.

    If you want something that just gets close to the mark, look at Jitsi. It’s about as complete as you could expect for just video/voice.

    What you may not understand about conferencing platforms is that they are dozens of different hosted services working together to provide a cohesive UE. Video, SIP, VOIP, auth, identity…these are all separate services that are deployed as microservices to get what you get. If you find the bare minimum of the services you actually need, you can probably cobble something together, but it’s not going to be a simple running of one service to get the same experience.



  • Don’t pull containers from random sources then. If you’re working with a specific project, only pull from their official images.

    Pushed images are built and verified from the maintainers, then pushed. Then you pull, each layer is verified by hash that it is the same image as was originally pushed by the maintainers.

    Whether that project protects itself from supply chain attacks is a different story, but as far as ports go, you only expose what you tell it to expose. There’s no workaround for that.





  • I’m confused by some of your questions, but it seems you are thinking that HDD vs SSD in the context of encryption is different, but it is functionally the same. Any perceived performance difference by percentage on HDD would be the same or better on SSD.

    I don’t think you’d perceive any slowdowns from encryption unless you’re doing very specific types of work and hitting the disk util hard, and even it would probably only be a few percentage points of difference between encrypted and unencrypted.

    You can find versions benchmarks online to compare different filesystem types and settings compared.


  • There are numerous automated systems for this, and almost every platform you use will have their own. Infiscal doesn’t seem bad, but I haven’t used it.

    I always suggest engineers just use whatever is closest to their stacks instead of implementing something, UNLESS it’s going to cost a lot more money (looking at you, AWS).

    Bitwarden/Vaultwarden+BWcli is also another workaround if you’re just using it for small projects.

    Etcd can do value encryption, and Redia even, but you should really be looking at something that has solid RBAC, or ZTC rotation.