From: "Ambrozewicz, Adrian" <adrian.ambrozewicz@linux.intel.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: ObjectMapper - quantity limitations?
Date: Wed, 27 Jan 2021 18:03:35 +0100 [thread overview]
Message-ID: <8fc3b7be-42bc-fc28-6bbd-c5d8de95feaf@linux.intel.com> (raw)
Hello,
I'm doing some performance measurements of OpenBMC telemetry subsystem.
I'm using my custom app, which spawns valid D-Bus Sensors, I configure
TelemetryService to monitor them and EventService to push MetricReports
to external server.
I observe certain limitation on my system. Each sensor is mapped as two
objects in ObjectMapper hierarchy. It seems that I am able to correctly
create up to 1500 sensors. When I go above this limit part of the
sensors are not represented in ObjectMapper tree.
Our use-case would most likely require creating even more sensors than
the limit I've reached now. I'm just starting to investigate the issue
and I would be happy if you could give me pointers or ideas what could
be the culprit here.
Regards,
Adrian
next reply other threads:[~2021-01-27 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 17:03 Ambrozewicz, Adrian [this message]
2021-01-27 17:14 ` ObjectMapper - quantity limitations? Ed Tanous
2021-02-09 15:36 ` Ambrozewicz, Adrian
2021-02-10 12:11 ` Andrew Jeffery
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8fc3b7be-42bc-fc28-6bbd-c5d8de95feaf@linux.intel.com \
--to=adrian.ambrozewicz@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.