I've been out for a bit, I'll bundle multiple replies in a single mail.
Before I start: thank you to everybody taking the time to respond in this
thread :)
How are you determining what you call "consumed memory"?
Memory which isn't available to the system. So "used" minus "buffers/cache"
Ke
On Thu, Apr 26, 2018 at 03:09:15PM +0200, Simon Beirnaert wrote:
> Hi Recently I've started moving a fleet of Debian 7, 32-bit machines over to
> Debian 9, 64-bit. This migration is done by creating a fresh Debian 9 image
> with the necessary services, moving over user data (some wars and the
> con
On 4/27/18, Reco wrote:
> Hi.
>
> On Fri, Apr 27, 2018 at 12:26:11PM +, Eduardo M KALINOWSKI wrote:
>> On sex, 27 abr 2018, Simon Beirnaert wrote:
>> > The bottom line for me is that I when I shut down everything I install
>> > and manage on the system, it's still conuming about half a g
On Fri 27 Apr 2018 at 12:26:11 (+), Eduardo M KALINOWSKI wrote:
> On sex, 27 abr 2018, Simon Beirnaert wrote:
> >The bottom line for me is that I when I shut down everything I install
> >and manage on the system, it's still conuming about half a gig more
> >than a system running the exact same
Hi.
On Fri, Apr 27, 2018 at 12:26:11PM +, Eduardo M KALINOWSKI wrote:
> On sex, 27 abr 2018, Simon Beirnaert wrote:
> > The bottom line for me is that I when I shut down everything I install
> > and manage on the system, it's still conuming about half a gig more
> > than a system runni
On sex, 27 abr 2018, Simon Beirnaert wrote:
The bottom line for me is that I when I shut down everything I install
and manage on the system, it's still conuming about half a gig more
than a system running the exact same base image right after use, without
the extra memory being accounted for by m
I'm not sure that a ratio of 512MB swap to 1.8GB RAM really proves
anything. If the swap space matched RAM in size and still filled up, I
think that would be more definitive.
The bottom line for me is that I when I shut down everything I install
and manage on the system, it's still conuming abou
On Thu, 26 Apr 2018 15:45:23 + Kenneth Parker
wrote:
> With the help of a "minimal" Debian 8 System, I am learning SystemD.
> My guess was, simply due to more "Moving Parts", than the prior Boot
> Process. More Open Processes, mean, practically more Memory Usage.
>
> Thanks!
>
> Kenneth Par
With the help of a "minimal" Debian 8 System, I am learning SystemD. My
guess was, simply due to more "Moving Parts", than the prior Boot Process.
More Open Processes, mean, practically more Memory Usage.
Thanks!
Kenneth Parker
On Thu, Apr 26, 2018, 11:18 AM David Wright
wrote:
> On Thu 26 Ap
On Thu 26 Apr 2018 at 15:01:38 (+), Kenneth Parker wrote:
> Couldn't be SystemD, could it? That wasn't in use, in Debian 7.
>
> Just a guess...
>
> Kenneth Parker
That's probably about as useful as saying "What do you expect?
You've moved from 32-bit to 64-bit, so double your memory."
> O
Couldn't be SystemD, could it? That wasn't in use, in Debian 7.
Just a guess...
Kenneth Parker
On Thu, Apr 26, 2018, 9:09 AM Simon Beirnaert <
simon.beirna...@lightspeedhq.com> wrote:
> Hi Recently I've started moving a fleet of Debian 7, 32-bit machines
> over to Debian 9, 64-bit. This migra
I'm not sure that a ratio of 512MB swap to 1.8GB RAM really proves
anything. If the swap space matched RAM in size and still filled up, I
think that would be more definitive. The bottom-line is that you need
to determine what's consuming it. Also note this comment at the top of
the stackexchange ar
Hi Recently I've started moving a fleet of Debian 7, 32-bit machines
over to Debian 9, 64-bit. This migration is done by creating a fresh
Debian 9 image with the necessary services, moving over user data (some
wars and the content of /home) and rebooting into the new OS.
Relevant services (one
13 matches
Mail list logo
