public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] KDE nepomuk memory usage
@ 2013-12-26 17:43 Alexander Puchmayr
  0 siblings, 0 replies; 5+ messages in thread
From: Alexander Puchmayr @ 2013-12-26 17:43 UTC (permalink / raw
  To: gentoo-user

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





^ permalink raw reply	[flat|nested] 5+ messages in thread

* [gentoo-user] KDE nepomuk memory usage
@ 2013-12-26 19:13 Alexander Puchmayr
  2013-12-26 22:42 ` Alan McKinnon
  0 siblings, 1 reply; 5+ messages in thread
From: Alexander Puchmayr @ 2013-12-26 19:13 UTC (permalink / raw
  To: gentoo-user

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




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] KDE nepomuk memory usage
  2013-12-26 19:13 Alexander Puchmayr
@ 2013-12-26 22:42 ` Alan McKinnon
  2013-12-27  6:50   ` Alexander Puchmayr
  0 siblings, 1 reply; 5+ messages in thread
From: Alan McKinnon @ 2013-12-26 22:42 UTC (permalink / raw
  To: gentoo-user

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



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] KDE nepomuk memory usage
  2013-12-26 22:42 ` Alan McKinnon
@ 2013-12-27  6:50   ` Alexander Puchmayr
  2013-12-27 10:54     ` Burak Arslan
  0 siblings, 1 reply; 5+ messages in thread
From: Alexander Puchmayr @ 2013-12-27  6:50 UTC (permalink / raw
  To: gentoo-user

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



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] KDE nepomuk memory usage
  2013-12-27  6:50   ` Alexander Puchmayr
@ 2013-12-27 10:54     ` Burak Arslan
  0 siblings, 0 replies; 5+ messages in thread
From: Burak Arslan @ 2013-12-27 10:54 UTC (permalink / raw
  To: gentoo-user

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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-12-27 10:54 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-26 17:43 [gentoo-user] KDE nepomuk memory usage Alexander Puchmayr
  -- strict thread matches above, loose matches on Subject: below --
2013-12-26 19:13 Alexander Puchmayr
2013-12-26 22:42 ` Alan McKinnon
2013-12-27  6:50   ` Alexander Puchmayr
2013-12-27 10:54     ` Burak Arslan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox