[gentoo-user] KDE nepomuk memory usage

[gentoo-user] KDE nepomuk memory usage

[Alexander Puchmayr]

Hi there,

How many memory is reasonable for virtuoso to use?
I just had a view via htop, and I was surprised to see virtuoso-t processes 
occupying more than 1.5 GB (!), althoug there is a maximum of 128MB defined.

Memory leak?

Versions involved:
dev-db/virtuoso-server-6.1.6
kde-base/kde-meta-4.10.5

Best regards
	Alex

Re: [gentoo-user] KDE nepomuk memory usage

[Alan McKinnon]

On 26/12/2013 21:13, Alexander Puchmayr wrote:
> Hi there,
> 
> How many memory is reasonable for virtuoso to use?
> I just had a view via htop, and I was surprised to see virtuoso-t processes 
> occupying more than 1.5 GB (!), althoug there is a maximum of 128MB defined.
> 
> Memory leak?
> 
> Versions involved:
> dev-db/virtuoso-server-6.1.6
> kde-base/kde-meta-4.10.5

What column in htop shows that number?

top, htop, and all their friends do not display what most people assume
they display. Modern OSes (for more than a decade now) manage memory in
a way that makes it impossible to answer "how much memory is this app
using?"

If you are looking at the VIRT column, just ignore it, that column is
practically useless for most rational viewings of {h,}top


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] KDE nepomuk memory usage

[Alexander Puchmayr]

On Freitag, 27. Dezember 2013, 00:42:06 Alan McKinnon wrote:

> What column in htop shows that number?
> 
> top, htop, and all their friends do not display what most people assume
> they display. Modern OSes (for more than a decade now) manage memory in
> a way that makes it impossible to answer "how much memory is this app
> using?"
> 
> If you are looking at the VIRT column, just ignore it, that column is
> practically useless for most rational viewings of {h,}top

I know, the VIRT column shows the size of the virtual adress space of the 
process, and this has nothing to do with the real, physical amount of memory 
allocated.

The RES column shows the resident memory, i.e. those pages actually in use and 
kept in memory, exclusive those pages swapped out. This column shows currently 
1185M (after rebooting this morning)


Best regards
	Alex

Re: [gentoo-user] KDE nepomuk memory usage

[Burak Arslan]

On 12/27/13 08:50, Alexander Puchmayr wrote:
> On Freitag, 27. Dezember 2013, 00:42:06 Alan McKinnon wrote:
>
>> What column in htop shows that number?
>>
>> top, htop, and all their friends do not display what most people assume
>> they display. Modern OSes (for more than a decade now) manage memory in
>> a way that makes it impossible to answer "how much memory is this app
>> using?"
>>
>> If you are looking at the VIRT column, just ignore it, that column is
>> practically useless for most rational viewings of {h,}top
> I know, the VIRT column shows the size of the virtual adress space of the 
> process, and this has nothing to do with the real, physical amount of memory 
> allocated.
>
> The RES column shows the resident memory, i.e. those pages actually in use and 
> kept in memory, exclusive those pages swapped out. This column shows currently 
> 1185M (after rebooting this morning)
>
>
>

I think the best way to measure how much memory a process is using is to
kill it and see how much memory is freed.

[gentoo-user] Re: KDE nepomuk memory usage

[Nikos Chantziaras]

On 26/12/13 21:13, Alexander Puchmayr wrote:
> Hi there,
>
> How many memory is reasonable for virtuoso to use?
> I just had a view via htop, and I was surprised to see virtuoso-t processes
> occupying more than 1.5 GB (!), althoug there is a maximum of 128MB defined.

KDE's "System Activity" (KSysGuard) is more accurate.

[gentoo-user] Re: KDE nepomuk memory usage

[James]

Alexander Puchmayr <alexander.puchmayr <at> linznet.at> writes:


> How many memory is reasonable for virtuoso to use?
> I just had a view via htop, and I was surprised to see virtuoso-t processes 
> occupying more than 1.5 GB (!), althoug there is a maximum of 128MB defined.

iotop (in portage) may help....?

There is another app, that I've never tried but folks rave
about, memtop, but it's not in portage.


A while back, I posted about Ftrace (function trace) and some
non portage ebuild, that may help.

hth,
James

Re: [gentoo-user] Re: KDE nepomuk memory usage

[Hinnerk van Bruinehsen]

James <wireless@tampabay.rr.com> wrote:
>Alexander Puchmayr <alexander.puchmayr <at> linznet.at> writes:
>
>
>> How many memory is reasonable for virtuoso to use?
>> I just had a view via htop, and I was surprised to see virtuoso-t
>processes 
>> occupying more than 1.5 GB (!), althoug there is a maximum of 128MB
>defined.
>
>iotop (in portage) may help....?
>
>There is another app, that I've never tried but folks rave
>about, memtop, but it's not in portage.
>
>
>A while back, I posted about Ftrace (function trace) and some
>non portage ebuild, that may help.

iotop shows io ( AS in reads and writes to disk). The only memory related info may be swap. You could try slabtop instead, but that isn't that informative either.
Maybe valgrind can hell if there really is a memory leak.

[gentoo-user] KDE nepomuk memory usage

[Alexander Puchmayr]

Hi there,

How many memory is reasonable for virtuoso to use?
I just had a view via htop, and I was surprised to see virtuoso-t processes 
occupying more than 1.5 GB (!), althoug there is a maximum of 128MB defined.

Memory leak?

Versions involved:
dev-db/virtuoso-server-6.1.6
kde-base/kde-meta-4.10.5

Best regards
	Alex