i hate it.

  • 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle







  • amigan@lemmy.dynatron.metoProgrammer Humor@lemmy.mlMy poor RAM...
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    10 months ago

    “Different inode” means a different file entirely, not necessarily its majorminor:inode tuple resolved through bind mounts/overlayFS/whatever. I’m saying that if you have containers using even slightly different base images, you effectively have n copies of libc in memory at once on the same system, which does not happen when you do not use containers.


  • amigan@lemmy.dynatron.metoProgrammer Humor@lemmy.mlMy poor RAM...
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    1
    ·
    edit-2
    10 months ago

    Except each container has its own libc and any other dependencies. If any linked binary or library has a different inode, it gets loaded separately. I would say it is indeed quite similar, even if the images in question here aren’t hundreds of megabytes in size like with Electron.


  • amigan@lemmy.dynatron.metoProgrammer Humor@lemmy.mlMy poor RAM...
    link
    fedilink
    English
    arrow-up
    53
    arrow-down
    2
    ·
    10 months ago

    It seems every new shiny technology today tries its darndest to short-circuit 40+ years of advances in OS virtual memory design. Between Electron and Docker, the entire idea of loading an image into memory once and sharing its pages among hundreds of processes is basically dead. But at least there’s lower support burden!!!1111