From: vjanandr85@gmail.com (Vijay Anand)
Subject: [lttng-dev] scale numbers for LTTNG
Date: Tue, 24 May 2016 11:31:02 +0530 [thread overview]
Message-ID: <CAHxF_R8QdRQjbgfE1d+Zgi=CmDiB6SEgL2Up1G-p21YdQz9pYA@mail.gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
Hello Folks,
We have been evaluating LTTNG for use in our production systems for user
space tracing. We have evaluated most of the features supported by LTTNG
and very much see a value add LTTNG brings into our debugging
infrastructure.
- Our current requirement is to trace Userspace programs running on
linux.
- Each of the linux processes define their own tracepoint providers.
- We would like to trace event histories of each process independently.
- We could potentially have 1000s of such processes running
simultaneously.
- We concluded on using a session/channel to trace one tracepoint
provider corresponding to a unique process.
- But I understand we could also create one system wide session and
use channels to trace each of the providers. Either of the
approaches seems
to work for us.
- But upon evaluating I see that we could create only 25 active
process-sessions and not traces from all the processes are logged.
- Please note I have tried increasing the buffer size and the number
of buffers. This doesn't help.
- Each of the process trace 52 events at and interval of 1 second
each.
- I have evaluated this with lttng in session,live and snapshot modes
and I have not been getting favourable.
Could you folks share the scale numbers that LTTNG supports, especially
when it comes to tracing user space programs ?
Regards,
Vijay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20160524/642feecd/attachment.html>
next reply other threads:[~2016-05-24 6:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 6:01 Vijay Anand [this message]
2016-05-26 12:23 ` Vijay Anand
2016-05-26 18:02 ` Jonathan Rajotte
2016-05-26 19:46 ` Mathieu Desnoyers
2016-05-30 7:16 ` Vijay Anand
2016-05-30 13:03 ` Mathieu Desnoyers
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='CAHxF_R8QdRQjbgfE1d+Zgi=CmDiB6SEgL2Up1G-p21YdQz9pYA@mail.gmail.com' \
--to=vjanandr85@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox