On Tue, 12 Oct 2021 09:46:04 +0200
"Ulrich Windl" wrote:
> >>> Jehan-Guillaume de Rorthais schrieb am 12.10.2021 um
> >>> 09:35 in
> Nachricht <20211012093554.4bb761a2@firost>:
> > On Tue, 12 Oct 2021 08:42:49 +0200
> > "Ulrich Windl" wrote:
> >
> ...
> >> "watch cat /proc/meminfo" could
On Tue, 12 Oct 2021 08:42:49 +0200
"Ulrich Windl" wrote:
> ...
> >> sysctl ‑a | grep dirty
> >> vm.dirty_background_bytes = 0
> >> vm.dirty_background_ratio = 10
> >
> > Considering your 256GB of physical memory, this means you can dirty up to
> > 25GB
> > pages in cache before the kernel
>>> Jehan-Guillaume de Rorthais schrieb am 11.10.2021 um
11:57 in
Nachricht <2021105737.7cc99e69@firost>:
> Hi,
>
> I kept the full answer in history to keep the list informed of your full
> answer.
>
> My answer down below.
>
> On Mon, 11 Oct 2021 11:33:12 +0200
> damiano giuliani wrote:
>>> Jehan-Guillaume de Rorthais schrieb am 09.10.2021 um
21:28 in
Nachricht <20211009212843.1c8469af@firost>:
...
> Indeed. But it's an arbitrage between swapping process mem or freeing
> mem by removing data from cache. For database servers, it is advised to use
> a
> lower value for
>>> damiano giuliani schrieb am 08.10.2021 um
>>> 15:00
in Nachricht
:
> Hi Guys, after months of suddens unexpected failovers, checking every
> corners and types of logs without any luck, cuz no logs and no reasons or
If you have no logs, you should cleaerly check your configuration.
...
>
>>> damiano giuliani schrieb am 23.07.2021 um
>>> 12:52
in Nachricht
:
> hi guys thanks for supporting.
> the time query isnt the problem, is known that took its time. the network
> is 10gbs bonding, quite impossible to sature with queries :=).
> the servers are totally overkilled, at database