Hi Ruben, That was it, it was set at 2.0, moved that to 1.0 and now 32 is 32 etc :)
-- Jimmy Van: Ruben Bosch <[email protected]> Datum: zaterdag, 9 december 2023 om 00:37 Aan: [email protected] <[email protected]> Onderwerp: Re: Memory not updated on instance Check out your memory overcommit ratio ;). Btw memory uses base 2 so 1 GiB is 1024 MiB (and thus 16GiB is 16384 MiB). Met vriendelijke groet / Kind regards, Ruben Bosch CLDIN > On 8 Dec 2023, at 23:23, Jimmy Huybrechts <[email protected]> wrote: > > So the strange part is that it seems to cut memory in half over what I > configure. > Just as an experiment I tried setting it at 32GB and I ended up with 16 in > Linux, is there some setting that is wreaking havoc? > > -- > Jimmy > > Van: Jimmy Huybrechts <[email protected]> > Datum: vrijdag, 8 december 2023 om 22:59 > Aan: [email protected] <[email protected]> > Onderwerp: Memory not updated on instance > Hi, > > I seem to have a bit of an odd issue. > > I created an instance first with 4GB of memory and 4 cores, after I found it > not to be enough I tried updating them by first shutting down the instance > and then just editing the settings to cpuNumber 12, Memory 16000. So 12 cpu’s > 16GB ram. > > After booting it I noticed it had 12 cpu’s as it should but only 8GB of > memory, stopped machine again and tried to scale it and do the same that way. > > Unfortunately it’s the same story, 12 cpu’s, 8GB memory. > > The instances dashboard clearly says 16GB memory. > > Running > 12 > 0.0 Ghz > 0.05% > 15.63 GiB > 5.33% > But this is the free -m from the Debian machine: > > free -m > total used free shared buff/cache > available > Mem: 7748 416 7365 2 193 > 7332 > Swap: 3813 0 3813 > > -- > Jimmy
