11–20 of 55 posts
Earlier quoted context omitted.
Problem with setting secure defaults, is that most of the worlds PHP would stop working properly.
Probably but you can still have the configuration secure as default and people would be aware of the security implications when enabling insecure features.
So at one point we where doing scale testing for our product where we needed to simulate systems running our software connected back to a central point. The idea was to run as many docker containers as we could on a server with 2x24 core and 512GB of RAM. The RAM needed for each container was very small. No matter what the system would start to break around ~1000 containers (this was 4 years ago). After doing may hou…
512GB RAM/2500 containers is still 500MB per container. In former days™ this was enough for a computer to run a complete desktop environment with a web browser and 20 tabs open (source: I had a PC with physically 500MB RAM). Is this really the limit for such a decent equipped machine? (I guess a server grade 48 cores, 512GB RAM should be less then 5kEUR nowadays)
Am I missing something? 512gb / 2500 is around 200mb per container.
Earlier quoted context omitted.
I've given up on expecting sane defaults from every piece of software. Some packages work perfectly fine out of the box, or simply work not at peak performance if not tuned slightly. Other software has so many dangerous default settings that it's hard to understand the rationale. Case in point for me is Docker itself. By default it will write logs to json-file and not truncate or rotate these logs. Packages distribut…
Could you point to some of the sane configuration for docker? We are planning to run some of these in production.
For the port-binding thing, I'd just remember that it binds to 0.0.0.0 when not explicitly specified otherwise, and then use docker network and not port-forwards unless absolutely needed. For example, if you have an application and a couple of backing services (database, redis, ElasticSearch), then only your application needs a port forwarded from the host, the rest can live within the docker network.
Earlier quoted context omitted.
512GB RAM/2500 containers is still 500MB per container. In former days™ this was enough for a computer to run a complete desktop environment with a web browser and 20 tabs open (source: I had a PC with physically 500MB RAM). Is this really the limit for such a decent equipped machine? (I guess a server grade 48 cores, 512GB RAM should be less then 5kEUR nowadays)
>512GB / 2500 is still 500mb per container Am I missing something? 512gb / 2500 is around 200mb per container.
Is there any talk of increasing these defaults in higher memory systems. The low defaults feel like foot guns that people stumble into rather than something needed for optimal performance.
I've given up on expecting sane defaults from every piece of software. Some packages work perfectly fine out of the box, or simply work not at peak performance if not tuned slightly. Other software has so many dangerous default settings that it's hard to understand the rationale. Case in point for me is Docker itself. By default it will write logs to json-file and not truncate or rotate these logs. Packages distribut…
Earlier quoted context omitted.
>512GB / 2500 is still 500mb per container Am I missing something? 512gb / 2500 is around 200mb per container.
I think he miscalculated. His point still stands, just not with 20 browser tabs.
They could easily double that density with Go, or quadruple with C++ or Rust. Why people still use JRE I fail to understand.
I'm a massive go and rust fan, but I don't expect the entire world to be re-written in them any time soon.
They could easily double that density with Go, or quadruple with C++ or Rust. Why people still use JRE I fail to understand.
Hopefully rootless docker completely eliminates the races by removing the kernel resource contention.