[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Top does not handle more than 100 cores

From: Pierre Gaston
Subject: Re: Top does not handle more than 100 cores
Date: Mon, 24 Mar 2014 16:00:16 +0200

On Mon, Mar 24, 2014 at 12:08 PM, Alexandre De Champeaux

> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
> -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
> -DSHELL -DHAVE_CONFIG_H   -I.  -I. -I./include -I./lib  -D_GNU_SOURCE
> -DRECYCLES_PIDS  -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fwrapv
> uname output: Linux isv 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36
> EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
> Machine Type: x86_64-redhat-linux-gnu
> Bash Version: 4.1
> Patch Level: 2
> Release Status: release
> Description:
>         The top command does not handle more than 100 cores. I also
> attached two screenshots of the issue, one showing the output of the  top
> command, and the other of a custom script showing the CPU usage per numa
> node (the server has 160 cores).
> Here is the ouptu of a top -v :
> address@hidden ~]# top -v
> top: procps version 3.2.8
> I did not try to reproduce on the latest version of top.
> Repeat-By:
>         Find a pretty cool machine with quite a bunch of cores, and run an
> highly parallel program :).
> --
> Alexandre

However, top is an external command and has nothing to do with bash, so you
need to report this to its authors, or to the package maintainer(s) of your

reply via email to

[Prev in Thread] Current Thread [Next in Thread]