#11 Make BBBP information optional in csv

[Fernando]

When having many CPUs the BBBP info is just too much.

I'm using nmon to monitor my server PC (64 cores). Just printing a /proc/cpuinfo generates around 88KB and 1792 lines at the top of the csv.

Currently I just commented some of the the BBBPs in the source code.

[Nigel Griffiths]

Fernando,
Yes these size of the /proc/cpuinfo file has grown over the years and it seems the kernel team or /proc guys do not have access to large servers with many CPUs.
I suggest you take this up with the Linux kernel deelopment team.
Unfortunately, on some hardware there are interesting stats at the bottom of the file and some tools may count the logical CPUs in the /proc/cpuinfo data.
Not many people read the .csv but use tools to extract what they want and/or draw graphs.
So I don't the size of this data is not an issue.
The benfit of truncating the BBBP section are minimal and the risks are high for breaking tools using nmon output .csv files.
Cheers,Nigel

[Fernando]

Understood!

But may be in case 'lscpu' is available nmon could just not print '/proc/cpuinfo', both print the "same " information. But as you say this not an issue... is just something that bothers me when I want to see the file with a text editor :-D.

Thanks for the response.