by DrinkWater on 4/13/23, 6:31 AM with 189 comments
by hghid on 4/13/23, 9:08 AM
by rwmj on 4/13/23, 9:04 AM
I think I see the problem already. Why does anyone think its a good idea to put everything in an embedded system into a container? Particularly as everything comes from a single vendor and so the usual argument about "but libraries are too hard!" doesn't apply.
by com2kid on 4/13/23, 6:24 PM
I've done this analysis for lots of software before, Windows has a really nice tool called Process Monitor that I've used to find huge slow downs before. Point it at a process and it'll tell you the every bit of IO that the application does, and at that point you can just start digging and opening bugs.
IMHO almost every piece of software of any significant size horribly misbehaves. Opening the same file again and again, writing out lots of tiny temp files, reading the same key from the registry (or some config file) over and over again , and worst of all, using fixed timeouts waiting for a task to complete instead of doing the work to make things properly event based.
On that last note, timeouts instead of event callbacks (or some sort of signaling system) is the cause of so much slowness across our entire industry. If something you are doing on a computer takes a human noticable amount of time, and you aren't throwing around tens of GBs of data or waiting on a slow network, then you are flat out doing something wrong.
by manojlds on 4/13/23, 10:19 AM
by scientism on 4/13/23, 11:05 AM
by kobalsky on 4/13/23, 7:30 PM
podman works fine until it doesn't. My hypothesis is that it has some fundamental design philosophy that makes it brittle. Properly cleaning up doesn't exist in their vocabulary.
For example, a cancelled download or image extraction can bring the whole thing down at the worst time, you have to hunt down the corrupted folder and remove so that anything works again.
A failed compose startup can leave the network in a undefined state hard to diagnose and impossible to recover without wiping some folders within /run/user and killing some rogue processes manually.
This is further cemented by the fact that a lot of minor issues are answered with: podman system reset, which reeks of rm -fr node_modules.
docker was always a pleasure to work with, I still don't understand why I suffered with podman so long.
by nickjj on 4/13/23, 12:55 PM
In 2018 I opened a github issue around container startup time[0] with Docker. A couple of things have changed since that issue but generally speaking we are talking about ~5s (containers) vs 150ms (no containers) to start a realistic process that depends on networking and other things you'd expect in a typical web app.
by anaganisk on 4/13/23, 12:50 PM
by jensenbox on 4/13/23, 6:34 PM
Folding a piece of paper (just like binary numbering) 6 times will provide you with a stack of 64 sheets.
They did not have a performance increase of 64 times.
This is identical to the idea of stating "magnitude" as being the number of times based on 10.
How wrong am I?
by mkoubaa on 4/13/23, 11:06 AM
by mongol on 4/13/23, 11:00 AM
by IceWreck on 4/13/23, 9:40 AM
by crest on 4/13/23, 8:11 AM
by perlgeek on 4/13/23, 10:16 AM
by shrubble on 4/13/23, 1:18 PM
by hamdouni on 4/13/23, 11:42 AM
Constraints (car env) drive creativity !
by polskibus on 4/13/23, 9:14 PM