From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Yuan Bin <elf.ggle@gmail.com>, lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] how to disable local file writing in relayd?
Date: Wed, 8 Mar 2023 09:45:01 -0500 [thread overview]
Message-ID: <d3af6ef9-1f99-f29f-b933-2a5d39a5ed0f@efficios.com> (raw)
In-Reply-To: <CAL_9pdTicspLuNH8UJ6=sSXuhHKLQOcq7GQC-NA0nmqSYENDzA@mail.gmail.com>
On 2023-03-06 00:12, Yuan Bin via lttng-dev wrote:
> Can I disable local-file-writing in lttng-relayd to avoid the disk
> space overhead, only using it as a live viewer?
Not explicitly, but you can store your temporary files on a tmpfs file
system (see lttng-relayd(8) --output command line parameter), which will
only keep the relayd files in memory, and use the tracefile rotation
feature to prevent the files from growing forever, e.g.:
https://lttng.org/docs/v2.13/#doc-enabling-disabling-channels
Example:Create a Linux kernel channel which rotates eight trace files of
4 MiB each for each stream.
lttng enable-channel --kernel --tracefile-count=8 \
--tracefile-size=4194304 my-channel
See lttng-enable-channel(1) for more info.
I hope this helps!
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2023-03-08 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 5:12 [lttng-dev] how to disable local file writing in relayd? Yuan Bin via lttng-dev
2023-03-08 14:45 ` Mathieu Desnoyers via lttng-dev [this message]
2023-03-22 6:39 ` [lttng-dev] Fwd: " Yuan Bin via lttng-dev
2023-03-22 13:25 ` Mathieu Desnoyers via lttng-dev
2023-03-24 10:44 ` Yuan Bin via lttng-dev
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=d3af6ef9-1f99-f29f-b933-2a5d39a5ed0f@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=elf.ggle@gmail.com \
--cc=mathieu.desnoyers@efficios.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;
as well as URLs for NNTP newsgroup(s).