diff options
| author | Abiola Asojo <abiola.asojo@ibm.com> | 2026-06-17 21:53:44 +0300 |
|---|---|---|
| committer | Andrew Geissler <geissonator@yahoo.com> | 2026-07-07 20:28:45 +0300 |
| commit | a9d3eb1593869a8ad0693bc6ceaceddfb40961f7 (patch) | |
| tree | 5b0fda8422f779dd26d692446b43322cafd4d12f /upstream-layers/meta-openembedded/meta-python/recipes-devtools/python/python3-bitarray_3.8.2.bb | |
| parent | 4b4d12b957731637a9b53a1e1bdd4e808dff95f4 (diff) | |
| download | openbmc-a9d3eb1593869a8ad0693bc6ceaceddfb40961f7.tar.xz | |
meta-ibm: Tune telemetry limits for 500+ sensors
Put max-append-limit at 4096.
The default max-append-limit is 256 [1]. The value is 16x higher, but
this testing showed no excessive telemetry memory use.
Updated max-reading-parameters to 1000. The reading parameters are set
here because we have more than 200 (the default value [2]) sensors in
our system, sometimes 500+.
[1]: https://github.com/openbmc/telemetry/blob/master/meson.options#L41
[2]: https://github.com/openbmc/telemetry/blob/master/meson.options#L13
Tested: Sensor readings were taken over several hours using the new
implementation that improves memory usage of AVG, MIN, MAX readings.
344 sensors were used.
Using the top command, memory usage for telemetry was monitored
and no excess memory usage was observed with these limits.
~# top | grep telemetry
368 1 root S 17648 2% 4% /usr/bin/telemetry
368 1 root R 17648 2% 0% /usr/bin/telemetry
Change-Id: I11a7ec4d4f3bd0a2206044fd8b6371f907a3c699
Signed-off-by: Abiola Asojo <abiola.asojo@ibm.com>
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Diffstat (limited to 'upstream-layers/meta-openembedded/meta-python/recipes-devtools/python/python3-bitarray_3.8.2.bb')
0 files changed, 0 insertions, 0 deletions