[
https://issues.apache.org/jira/browse/METRON-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798874#comment-15798874
]
ASF GitHub Bot commented on METRON-636:
---------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/400
Thanks for the explanation @anandsubbu . Glad we agree on going after
'static' system information. That makes sense to me.
What information specifically do you want to capture? Amount of physical
memory? Number of CPU cores?
As is, the script spits out more dynamic information than static, in my
opinion. Maybe the script could filter out some of the other elements that
might be more distraction than useful. For example, on my Mac...
```
$ top -l 1 | head -10 2>/dev/null
Processes: 363 total, 2 running, 361 sleeping, 1735 threads
2017/01/04 12:42:04
Load Avg: 2.19, 1.87, 1.55
CPU usage: 22.54% user, 19.7% sys, 58.38% idle
SharedLibs: 167M resident, 37M data, 45M linkedit.
MemRegions: 129777 total, 5335M resident, 189M private, 1860M shared.
PhysMem: 13G used (2764M wired), 2753M unused.
VM: 1076G vsize, 620M framework vsize, 3733004(0) swapins, 3839813(0)
swapouts.
Networks: packets: 7978036/7950M in, 4748808/532M out.
Disks: 7485876/92G read, 2696358/81G written.
```
> Capture memory and cpu details as a part of platform-info script
> ----------------------------------------------------------------
>
> Key: METRON-636
> URL: https://issues.apache.org/jira/browse/METRON-636
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.3.0
> Reporter: Anand Subramanian
> Assignee: Anand Subramanian
> Priority: Minor
>
> The platform-info.sh script currently does not capture the system memory
> footprints.
> Many issues reported by users when deploying quick dev or full dev single
> node deployments are due to system constraints (low memory for e.g.). It
> would be good to enhance the platform-info script so that it can ease out
> finding potential resource issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
