Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t7xG8-001Dtx-Ix for pgsql-general@arkaria.postgresql.org; Mon, 04 Nov 2024 13:36:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t7xF7-001NsA-QF for pgsql-general@arkaria.postgresql.org; Mon, 04 Nov 2024 13:35:42 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t7xF7-001NrV-BY for pgsql-general@lists.postgresql.org; Mon, 04 Nov 2024 13:35:42 +0000 Received: from mail-vk1-xa31.google.com ([2607:f8b0:4864:20::a31]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t7xF1-0008Jz-5J for pgsql-general@lists.postgresql.org; Mon, 04 Nov 2024 13:35:40 +0000 Received: by mail-vk1-xa31.google.com with SMTP id 71dfb90a1353d-50d479aef64so1401860e0c.0 for ; Mon, 04 Nov 2024 05:35:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dbtune.com; s=google; t=1730727334; x=1731332134; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=LpZlvUDRffERIpoqYKG+ixXpeL6fdpR17TqOVaTy4GE=; b=Lw9DwDExrXHTfkgcofKqdMvv733qMuqZZl1cv6OqykOfk8Qf/oRvS1+j3r7ogKYzpZ HvwNWUTQeCXxPpujGnGHyu4EAg0OfwY1oKtWa93SSOwonisRi1iNFjS9kd43F+2SSa0t UBxwUjHcWY2p88zpHNfkE9zJSUicwGEaIZvCdoHdcskvPZtOWeWR8JsZzMyOtvd9cS3v FpQFfd7M11nl+AL/zEOz8QAW9dIKQbO5Tg40BHeCAI15B+JCbXd6lhpQSFyLT0UAgnR0 GlyzMP+NNQyB90rYqTOgCY5K6h4Pa+bHdM4u5oUD8fJ7vNCwjY8WAOn/E9RGdmQ7vabs PkUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730727334; x=1731332134; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=LpZlvUDRffERIpoqYKG+ixXpeL6fdpR17TqOVaTy4GE=; b=MCurSt6nziasRc8R2PP1ni1V3xMyrVfNWM0PQ6HwDetckumXx1SGOhv/jqJkkPUj5s WOJNz0U2sdjk0TWR3MdwRT0aZpbyvfRkKa3dZSWBfpnwMj27GoD+U73tDr90/em+Wcf5 D8Mq/cXVljdsaX3aH0Ie0NEW7X0DyeQtFoX8AL6bLZd2IlmEs/w4rF30iuZHeEUZX+N0 3PGzYaH6adqaJOrqMpjDTH5uXFXAumSx9QhML5iRmdd1O2+SZ50Ho7mdD1u0hDOi6a/q VS44AMKNMg4RVuRgGcUi0/P/70CCnZtHhlaBafH5XZZOt6o0DRMdyTwXEfKH97WZwoRZ L4pA== X-Forwarded-Encrypted: i=1; AJvYcCWcUhTFLSdn0F0SUJARGYiHVcwvRPKQpWNC/exf4DdW0tTG7/UfhWS45Vl0VNmog+FmwZysl/sWjQ0AIHXK@lists.postgresql.org X-Gm-Message-State: AOJu0YyS/zdvhEtrdnPSWzj76Skm6W2/13tennXrrY/eXdDAMU5cJadI QcEQwxTpmy7jIBrE8rmSrpFhfDnsB0cErmhZlTU1tbqNAItsNwkYlhjltkkJyurO3YPMDpr3RNP +BkyeRvTjFDgmLkYPja8hePGfzYW/wmwQNgK9va7AxEb7IrPq/7q4tg== X-Google-Smtp-Source: AGHT+IHuqFWqq0l1z8C/bHqXsPf/LRA/hVaN8RV6a7d8Wpn1cRMoIKB+UHrh9H71Ra62KKEQYw7Syib8kKdnFNULiC4= X-Received: by 2002:a05:6122:46a9:b0:501:2556:1cd9 with SMTP id 71dfb90a1353d-51227359c0fmr10777539e0c.10.1730727333770; Mon, 04 Nov 2024 05:35:33 -0800 (PST) MIME-Version: 1.0 References: <20241101195617.xkexgtwuyeo2hvmx@hjp.at> In-Reply-To: <20241101195617.xkexgtwuyeo2hvmx@hjp.at> From: Costa Alexoglou Date: Mon, 4 Nov 2024 14:35:23 +0100 Message-ID: Subject: Re: Used memory calculation in containers - docker stats and file cache To: hjp-pgsql@hjp.at, pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000eed96c0626165b00" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000eed96c0626165b00 Content-Type: text/plain; charset="UTF-8" > I don't know if Docker does anything strange here. I am not sure if this is docker specific or cgroup comes into play. The measurement is implemented in docker CLI, but I would make the assumption that the eviction is done within the cgroup scope. > A large file (or many smaller files) which is cached is deleted The increase pattern is "incremental" until the huge eviction, and this is my question. Couldn't also the eviction happen incrementally rather than 15GB of file cache evicted on an instant? > So I'd double check the logs if there are any errors. Not any error in the logs, unfortunately (or fortunately). Seems like this issue , or the parent one that everyone is linking to this. --000000000000eed96c0626165b00 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> I don't know if Docker does anything strange here= .

I am not sure if this is docker specific or cgroup com= es into play.=C2=A0
The measurement is implemented in docker CLI,= but I would make the assumption
that the eviction is done within= the cgroup scope.

> A large file (or many smal= ler files) which is cached is deleted

The increase= pattern is "incremental" until the huge eviction, and this is my= question.
Couldn't also the eviction happen incrementally ra= ther than 15GB of file cache evicted on an instant?

> So I'd double check the logs if there are
any errors.
Not any error in the=C2=A0logs, unfortunately=C2=A0(or fortunately).
=

Seems like this issue, or the parent one=C2=A0that everyone is linking to= this.
--000000000000eed96c0626165b00--