Tag Info

New answers tagged

0

PAE doesn't change anything about virtual addresses. As the name hints, it's only about physical addresses. As an application programmer, PAE doesn't change anything for you. Your program still has a 32-bit address space, out of which the kernel takes approximately 1 bit (Linux grants 1GB, 2GB or 3GB to userspace depending on compilation options). If you ...


0

pae stand for physical address extension and allow a cpu with a 32bit address bus to address more than 4G. Notice that if your /proc/cpuinfo show support for pae isn't enough, you need to use a kernel compiled with pae options enabled (eg: I'm using a Debian prebuilt 3.16-2-686-pae) The memory model/layout of a Linux process is defined by the Linux kernel ...


0

The original question seems to have been for a Mac, but for anyone else stumbling across this answer, on Red Hat Linux (and many others), 'top -m' starts top with results sorted by memory usage.


2

You could - probably. From the man page: While this is a good point in terms of report speed and safeness, this also makes the presented information possibly unreliable. You'll also still need to work out exactly what type and what speed that you'll need for your laptop. Why not use http://www.crucial.com or a similar site and enter the details ...


1

The setrlimit(2) syscall is relevant to limit resources (CPU time -integral number of seconds, so at least 1 sec- with RLIMIT_CPU, file size with RLIMIT_FSIZE, address space with RLIMIT_AS, etc...). You could also set up disk quotas. The wait4(2) syscall tells you -and gives feedback- about some resource usage. And proc(5) tells you a lot more, and also ...


-1

I use a little awk get the top10 memory users based on the resident set size (RSS) that is the amount of memory a process actually uses in your servers RAM (without swapped pages): awk '{ printf "%8d %8d %8d pid:%-5d comm:%-10s state:%c\n",$14,$15,$24,$1,$2,$3; }' /proc/[1-9]*/stat |sort -rn -k3 |sed 10q without the sed 10q you get the full list of ...


0

In addition to the tools from daemontools suggested by Mark Johnson, you can also consider chpst whish is found in runit. Runit itself is bundeled in busybox hence, you might already have it installed. The man page of chpst shows the option: -m bytes limit memory. Limit the data segment, stack segment, locked physical pages, and total of all ...



Top 50 recent answers are included