I'am Sorry ...
When I run this command, I get :
root@beaglebone:/home/debian# top -o '%MEM'
top - 00:07:42 up 14 min,  1 user,  load average: 0.66, 1.51, 1.67
Tasks:  93 total,   1 running,  65 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.7 us,  1.3 sy,  0.0 ni, 98.0 id,  0.0 wa,  0.0 hi,  0.0 si,
0.0 st
KiB Mem :   494588 total,    24908 free,   409256 used,    60424 buff/cache
KiB Swap:  1048572 total,   956924 free,    91648 used.    71880 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND

 1492 root      20   0  484960 361796  11372 S  0.0 73.2   6:32.76 node

 2069 root      20   0    9656   4840   4096 S  0.0  1.0   0:00.13 sshd

 2071 debian    20   0    8156   4684   4032 S  0.0  0.9   0:00.15 systemd

 2076 debian    20   0    9656   3728   2956 S  0.0  0.8   0:00.06 sshd

 2077 debian    20   0    5568   3604   2212 S  0.0  0.7   0:00.34 bash

 1254 mysql     20   0  593356   3556   2564 S  0.3  0.7   0:02.62 mysqld

    1 root      20   0   25492   3432   2740 S  0.0  0.7   0:03.53 systemd

  891 root      20   0    6064   3020   2772 S  0.0  0.6   0:00.15
systemd-logind

 2086 root      20   0    6272   2884   2476 S  0.0  0.6   0:00.05 sudo

 2090 root      20   0    7044   2820   2292 R  1.0  0.6   0:00.81 top

 2087 root      20   0    6032   2636   2268 S  0.0  0.5   0:00.02 su

 2088 root      20   0    4596   2628   2208 S  0.0  0.5   0:00.02 bash

 2072 debian    20   0   26964   2296   1336 S  0.0  0.5   0:00.00
(sd-pam)

  772 root      20   0   22592   2144   1960 S  0.3  0.4   0:11.96
systemd-journal

  827 systemd+  20   0   15948   1864   1720 S  0.0  0.4   0:00.98
systemd-timesyn

  897 message+  20   0    5324   1500   1292 S  0.0  0.3   0:00.37
dbus-daemon

 1265 dnsmasq   20   0    7940   1328   1228 S  0.0  0.3   0:00.54 dnsmasq

  927 root      20   0   22200   1112    844 S  0.0  0.2   0:04.29
rsyslogd

 1032 root      20   0    8500    956    864 S  0.0  0.2   0:00.07 sshd

  788 root      20   0   14104    848    784 S  0.0  0.2   0:02.79
systemd-udevd

  882 avahi     20   0    5324    796    680 S  0.0  0.2   0:00.28
avahi-daemon

  870 root      20   0    4628    636    588 S  0.0  0.1   0:00.03 cron

 1068 root      20   0    6496    636    580 S  0.0  0.1   0:00.12 apache2

 1079 www-data  20   0  228896    364    308 S  0.0  0.1   0:00.65 apache2

 1077 www-data  20   0  228896    360    304 S  0.0  0.1   0:00.65 apache2

  901 avahi     20   0    5200      8      0 S  0.0  0.0   0:00.00
avahi-daemon

  979 root      20   0    4404      8      4 S  0.0  0.0   0:00.02 bash

  836 root      20   0    7216      4      4 S  0.0  0.0   0:03.56 haveged

  876 daemon    20   0    2968      4      4 S  0.0  0.0   0:00.01 atd




Le sam. 1 sept. 2018 à 15:30, Dennis Lee Bieber <[email protected]> a
écrit :

> On Fri, 31 Aug 2018 22:29:32 +0100, Ichrak Mansour
> <[email protected]> declaimed the
> following:
>
> >This is how I created my swap file :
> >[image: swaap.png]
> >
>
>         And once again you attach an 80MB IMAGE that is unusable for
> cut&paste
> into a command line. I don't write code in a paint program. In the future,
> I will ignore any message with an image of a screen capture where text
> cut&paste would be useful.
>
>         In a second console window, run
>
> top -o '%MEM'
>
> and monitor the display while running whatever is using up memory. That
> /should/ put the main memory hog process at the top of the list. You should
> also be seeing the summary row for "KiB Swap" showing total swap usage.
> (NOTE: you have to watch this live, since as soon as the OOM kill takes
> place, that process will disappear from the display).
>
>         If the total swap usage is still running out, I can only suggest
> trying
> with a larger swap file (one reason I also recommend using a USB hard-drive
> -- since each GB of swap is 15% of an 8GB SD card, and a process using a
> lot of swap /could/ wear out the SD card [depends on if it is just
> allocating and writing to swap vs thrashing stuff in and out of swap
> space]).
>
>         If it still gets OOM killed with 2 or 4 GB swap -- I'd think there
> is
> something wrong with the program you are running. The only time I've had
> OOM kills was when I was running the HINT benchmark (about two years ago)
> and had to put in that hard drive for swap (I /did/ kill a Raspberry-Pi SD
> card with that benchmark before re-running using the drive on it). HINT,
> however, is smart-enough to detect when the run-time on swap grows rapidly
> and ends the benchmark run at that time. On a bare-board embedded system,
> HINT ends the run when malloc() returns 0 memory -- apparently Linux kills
> the process rather than having malloc() fail.
>
>
> --
>         Wulfraed                 Dennis Lee Bieber         AF6VN
>         [email protected]    HTTP://wlfraed.home.netcom.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/4i4lod9cjjnfl7k1hh5m32u4s07phnn6t2%404ax.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

   * ICHRAK Mansour*

Etudiante en ingénierie Téléinformatique
Université de Sousse - ISITCOM
*T :*  +216 52 650 216
*M :* [email protected]

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CACtBPxPFL7DySb6uK%2BmDDf2O9dhT-Cg6th7d3DAX84p2%2BXZfLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to