Sorry for the noise.
Sunny Naqvi
On Fri, Apr 20, 2018 at 05:08 PM, Janne Johansson wrote:
2018-04-20 14:54 GMT+02:00 :
Hi,
Can you explain me how to use vmstat to detect which software are taking
more memory ?
Instead of asking every little detail about this OS, one mail at a time,
could I
vmstat can't be used for that.
Use top(1) and check its SIZE (virtual mem size) and RES (mem currently in
RAM) columns.
You can also use ps(1) with -m argument to sort by memory usage.
It has %MEM (compared to other processes), RSS (like RES), VSZ (like SIZE)
read man pages for ps and top:
2018-04-20 14:54 GMT+02:00 :
> Hi,
> Can you explain me how to use vmstat to detect which software are taking
> more memory ?
>
>
Instead of asking every little detail about this OS, one mail at a time,
could I suggest
you read the FAQ, the manpages and in this partic
Hi,
Can you explain me how to use vmstat to detect which software are taking more
memory ?
Thank's
Sunny Naqvi
Hi,
I have constant number of blocked procs in vmstat after xfce starts
when system-wide dbus is enabled in pkg_scripts on my laptop:
pacija@efreet:~ $ vmstat 1 10
procsmemory pagedisk traps cpu
r b wavm fre flt re pi po fr sr sd0 int
> On Sat, Mar 01, 2014 at 21:34, Denis Fondras wrote:
> > Hi all,
> >
> > I've just discovered that OpenBSD vmstat(8) can use wait and count
> > arguments without using -c/-w. Here is a small patch to mention this
> > usage in the manual :
>
> This is
On Sat, Mar 01, 2014 at 21:34, Denis Fondras wrote:
> Hi all,
>
> I've just discovered that OpenBSD vmstat(8) can use wait and count
> arguments without using -c/-w. Here is a small patch to mention this
> usage in the manual :
This is a holdover from olden days. If I could
On Mon, Mar 03, 2014 at 04:03:08PM +, Jason McIntyre wrote:
> On Sat, Mar 01, 2014 at 09:34:10PM +0100, Denis Fondras wrote:
> > Hi all,
> >
> > I've just discovered that OpenBSD vmstat(8) can use wait and count
> > arguments without using -c/-w. Here
On Sat, Mar 01, 2014 at 09:34:10PM +0100, Denis Fondras wrote:
> Hi all,
>
> I've just discovered that OpenBSD vmstat(8) can use wait and count
> arguments without using -c/-w. Here is a small patch to mention this
> usage in the manual :
>
> Regards,
> Denis
>
&
Hi all,
I've just discovered that OpenBSD vmstat(8) can use wait and count
arguments without using -c/-w. Here is a small patch to mention this
usage in the manual :
Regards,
Denis
--- vmstat.8.orig Sun Feb 23 15:50:17 2014
+++ vmstat.8Sun Feb 23 15:54:24 2014
@@ -45,6 +45,11 @@
hi there,
i meant to ask this for some time but i always forget.
amaaq$ vmstat -i
interrupt total rate
irq0/clock 26305056 99
irq130/acpi0264720
irq82/azalia0 9429503
irq83/iwn0
On Wednesday 16 July 2008, Daniel Barowy wrote:
> Hello everyone,
>
>Can someone here shed some light on why my vmstat might have
> negative values? If I understand the manpage correctly (and Henning
> and Phillipp's paper on tuning), these values are nonsensical:
>
Hello everyone,
Can someone here shed some light on why my vmstat might have negative
values? If I understand the manpage correctly (and Henning and Phillipp's
paper on tuning), these values are nonsensical:
$ vmstat wd0 wd1 sd0
procs memorypage
Maxim Bourmistrov wrote:
> vmstat -m reports negative value for UVM amap Requests.
...
> ===> UVM amap 87670 8352K 28908K157284K-20682868430 0
> 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768
That is just a 32 bit signed integer wrapping around, probably because
your
Hi!
vmstat -m reports negative value for UVM amap Requests.
Any ideas why? Bug?
This is a i386, MP, 3.9-stable.
susbject related vmstat output:
Memory statistics by type Type Kern
Type InUse MemUse HighUse Limit Requests Limit Limit Size(s)
devbuf
Hi!
This is a i386 3.9 MP machine.
Bug?
Memory statistics by type Type Kern
Type InUse MemUse HighUse Limit Requests Limit Limit Size(s)
devbuf 901 361K558K157284K2962728660 0
16,32,64,128,256,512,1024,2048,4096,8192,16384,32768
On Sun, Sep 04, 2005 at 09:31:36PM +0200, Vincent Immler wrote:
>
> What does this output mean? Is someone able to explain this output to me?
>
> /* not copying files*/
> soekris# vmstat -i | grep hifn
> irq11/hifn0397322 488
>
> /* start t
tried to ensure that the vpn1401 card is working, but did not found
any possibility. Best I found was:
soekris# vmstat -i | grep hifn
irq11/hifn0379322 573
What does this output mean? Is someone able to explain this output to me?
/* not copying files*/
soekris# vmstat -i
18 matches
Mail list logo